Hi,
When using this component on a tablet (specifically, Safari on an Ipad), when scrolling down it results in a "429 Too many requests" error and doesn't load any more data. For the same web app on a computer, it works fine.
Any ideas on how to fix this?
How is the data being refreshed? Where does the 429 error originate from?
I don't know the specific component, but it seems weird that there is a difference per device. As a potential fix: is it possible to get more records on each refresh, to reduce the number of requests done?
Hi Leon,
I tried to simulate on an iPad device, and didn't get the error I said.
Here is a demonstration: https://jah.outsystemscloud.com/infinitecrolldemo/
Regards
Hi Leonardo,
Sorry for the late reply. The Ipad we use for testing was in the office.
With regards to your solution, we are using the infinite scroll in combination with an API call.
I also tried building it with an aggregate, and that works without issues.
I tried implementing the following:
Added an "IsFetched" variable to the GetLogs action to simulate the "IsDataFetched" attribute. It is set to false at the beginning of the action, and true at the end.
The second statement checks if the API call returns any records.
If there are still records to be retrieved it increases the page parameter for the API and calls again.
My guess would be that on a tablet this actions is triggered to often and it somehow calls the API many times. Weirdly this behaviour doesn't happen on a 'normal' browser.