ShotGrid REST API Pagination and Data Consistency
0 reputation · 18 Jun 2020, 21:18 UTC
Entity Retrieval via REST API
When synchronizing large datasets from ShotGrid (Autodesk Flow Production Tracking), the REST API requires pagination to manage result sets and avoid server timeouts. The system utilizes tokens or offset markers to navigate through these pages of entity data.
Concurrent Update Constraints
A challenge arises when entities are modified or created while a paginated read sequence is in progress. Because the API must maintain a stable result set across multiple requests, there is uncertainty regarding how the server handles shifts in the underlying data index during active pagination.
- Potential for duplicate records if an entity moves to a subsequent page.
- Risk of skipping records if an entity is deleted or moved to a previous page.
What is the documented behavior for maintaining result set integrity during concurrent updates? Does the API provide a snapshot-based mechanism to ensure a consistent view of the data across all pagination tokens?
shotgrid