Forum Discussion

joshieboy's avatar
joshieboy
Frequent Visitor
2 years ago
Solved

Auto refresh report disabled because of error

Hello,

I am literally stumped as to how to go about resolving this error.  The auto refresh for my reports have been disabled as a result of it.

 

DataSource.Error: <ccon>OData: Request failed: The remote server returned an error: (429). (429 TOO MANY REQUESTS). DataSourceKind = OData. DataSourcePath = https://xxx/sites/pwa/_api/ProjectData/[en-us]/TaskTimephasedDataSet. SPRequestGuid = 142cb6a0-c004-3000-840a-07ed74c2d990. Url = https://xxx/sites/pwa/_api/ProjectData/[en-us]/TaskTimephasedDataSet?$select=ProjectId,ProjectName,TaskActualCost,TaskActualWork,TaskCost,TaskId,TaskName,TaskWork,TimeByDay&$skiptoken=guid'1c55b0c0-c53e-ea11-ad6f-8019345eec90',guid'48c00ba4-1d50-eb11-be6f-c0b8838466b4',datetime'2019-05-07T00:00:00'. </ccon>. 

  • To resolve the error you issue fewer request, less frequently.

  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi joshieboy 

     

    The 429 too many requests error occurs when the server detects an excessive number iof requests from your application or service within a short time frame.

    You can try to optimize queries.

    Or you can check if there are some conflicting datasets refreshing in parallel, and avoid parallel refreshes during this time.

    And you can consider scheduling your dataset refresh at midnight(when resource usage is typically lower).

    If possible, consider upgrading to Premium capacity to allocate more resources for data refresh.

     

    Best Regards

    Zhengdong Xu
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

2 Replies

  • To resolve the error you issue fewer request, less frequently.

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi joshieboy 

     

    The 429 too many requests error occurs when the server detects an excessive number iof requests from your application or service within a short time frame.

    You can try to optimize queries.

    Or you can check if there are some conflicting datasets refreshing in parallel, and avoid parallel refreshes during this time.

    And you can consider scheduling your dataset refresh at midnight(when resource usage is typically lower).

    If possible, consider upgrading to Premium capacity to allocate more resources for data refresh.

     

    Best Regards

    Zhengdong Xu
    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.