You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This API call took more than 2 minutes to load (2.40 sec exactly). The user is trying to load the results based on the columnlast_index which is used for pagination. When last_index column is used usually it takes a while to load the results.
I am going to research more on the last_index column and see how it impacts the API results.
In SA table there are 230+million records. Since Schedule A consists of large number of transactions paginating using last_index makes the query a little complex.
I tried to paginate thru next page of results by providing the last_index=4082420181586122237 and the last_contribution_receipt_date=2018-04-19T00:00:00. The API returned results using next page in under a minute.
From an email to the Information Division:
We'll let him know it's been reported to the website team for investigation.
The text was updated successfully, but these errors were encountered: