Keep data synchronized in case of a HTTP error code (e.g. 429)

[fredeckbert]

Example: In a Free plan, 9500 rows have already been added to a push dataset in the current hour. The next POST request to add another 1000 rows fails with a 429. What exactly is happening with this 429? Were 0 or 500 rows added?

Background: If I want to send updates to a row by inserting a new row, I don't know if the row has really been transferred in case of an error and I'm losing the ability to keep the data in sync. I would like to avoid sending a separate request for each row to be added.

[v-ljerr-msft · Accepted solution]

Hi @fredeckbert,

Based on my research, receiving a status 429 is not an error, it is the other server "kindly" asking you to please stop spamming requests. Obviously, your rate of requests has been too high and the server is not willing to accept this. So there should be 0 row(no rows) added in this scenario.

You can find more information on status 429 here: http://tools.ietf.org/html/rfc6585#page-3

Regards