We've run into this internally: if any of the functions that retrieve data from paginated endpoints (e.g. list_tickets()) hit an API rate limit, they fail out without handling the rate limit exception or returning any of the data retrieved so far.
Ideally, the code collating the pages should check for 429 responses and throttle and retry.
We've run into this internally: if any of the functions that retrieve data from paginated endpoints (e.g.
list_tickets()) hit an API rate limit, they fail out without handling the rate limit exception or returning any of the data retrieved so far.Ideally, the code collating the pages should check for 429 responses and throttle and retry.