Pagination cursor expires too quickly
#10
Our nightly sync job sometimes gets an expired cursor error halfway through a large export. What is the actual cursor TTL?
Solution
meowOwnerThe cursor TTL is 15 minutes. A nightly sync over a large dataset can outlive that if it stalls partway through, so the safest pattern is to persist the cursor after each page and resume from the last saved one instead of holding the whole run in memory.
2 replies
meowOwner✓ Solution
The cursor TTL is 15 minutes. A nightly sync over a large dataset can outlive that if it stalls partway through, so the safest pattern is to persist the cursor after each page and resume from the last saved one instead of holding the whole run in memory.
Switched to persisting the cursor after each page like suggested, no more expired cursor errors.
Sign in to reply to this question.
Powered by Forumcat