Max Rate Limit Delay
The maximum amount of time to delay (in seconds) before submitting a request if it would be rate limited.
Twitter uses different rate limits for total number of requests for different endpoints. These can range from as few as 15 per 15 minute window, up to 900 for a 15 minute window. Internally the CData JDBC Driver for Twitter Ads keeps track of if a given request would result in a rate limit exception. If a rate limit would occur, the CData JDBC Driver for Twitter Ads can internally delay submitting a request until the limit is up. However, this could also result in waiting for several minutes before requesting data, which is also not a good behavior.
The MaxRateLimitDelay gives control over the maximum amount of time the CData JDBC Driver for Twitter Ads will wait once it detects a rate limit would occur. Since the amount of time the CData JDBC Driver for Twitter Ads needs to wait can be calculated, if it would have to wait longer than the MaxRateLimitDelay, it will simply error immediately when it sees the time would take too long.