OData Requests Failing Returning Error 429 Too Many Requests

Questions
1

Our OData requests have stopped working returning an error:

OData:
Request failed:
The remote server returned an error:
(429) Too Many Requests. (Too Many Requests)

The requests aren’t showing in monitoring live but there is the following error:

image
image1796×768 49.6 KB

2

A sample has been located as request ID 0HNJ527DH0AL4:00000003.

The statistics are:

Aspect Used
Platform: rows 997.269
Platform: bytes 1.100.900.783
Platform: duration (ms) 3.,202.901
Platform: requests 997
Platform: API calls fresh 993
Platform: API calls cached 4
Platform: API rows fresh 997.031
Platform: API rows cached 238
OData4: fresh rows 74.007
OData4: fresh bytes 2.443.247
OData4: fresh requests 13

Initial analyses revealed that the following maximum limits are currently not defined:

  • Maximum number of API calls per day, fresh and cached
  • Maximum number of API calls per day, fresh only
  • Maximum number of thousand API rows processed per day, fresh and cached
  • Maximum number of thousand API rows processed per day, fresh only

It is unsure whether this is the cause of the error.

These limits have been reloaded. Corrections have been made to ensure that the limits are not being dropped.

Can you please retry the downloads?

If the error still occurs on the Free Plan, please search for “429” in Invantive Monitoring and include the request ID in your reply.

3

Thank you, it is still happening, there were 51 entries in Invantive monitoring, with the timestamp of the refresh just attempted.

The first Request ID is: 0HNJ527DH0E1H:00000001

4

The logging indicated on itgenboe378 message that the Free Plan limits are exceeded.

The total processing time 3833 seconds with approximately 1 million rows internally processed. This exceeds the limits on rows processed and duration.

Sample Query 1

The following query retrieves timesheets for four years, download approximately 240K rows from Autotask:

select t.[id], t.[createDateTime], t.[dateWorked], t.[hoursWorked], t.[internalBillingCodeID], t.[internalNotes], t.[isNonBillable], t.[resourceID], t.[roleID], t.[ticketID], t.[timeEntryType]
from   Autotask.TimeEntries.TimeEntries@at t
where  (([createDateTime] >= :w1) and ([createDateTime] < :w2))

Sample Query 2

The following query retrieves some columns on service level agreement results (131,416 rows):

select t.[id], t.[firstResponseElapsedHours], t.[firstResponseResourceID], t.[resolutionElapsedHours], t.[resolutionPlanElapsedHours], t.[resolutionPlanResourceID], t.[resolutionResourceID], t.[ticketID]
from   Autotask.ServiceLevelAgreementResults.ServiceLevelAgreementResults@at t

There are several other heavy queries, which can be found in the Monitoring section.

It is recommended to either optimize the queries to reduce data volume and especially run time by better filters or caching.

More details can be found by consulting:

5

Today, February 10, 2026, a correction has been implemented: the number of API rows and API calls were counted twice when using Power BI. This made it possible to exceed the limit of the Free Exact Online Plan with just 50,000 rows.

The problem should now be resolved and affected users who were approaching the 100,000 row limit.

We apologize for the inconvenience.