Handle provider rate limits without skipping contacts
The importer treats a rate-limited page as empty and advances.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Retries · HTTP
Estimated field mix
- Integrations60%
- Site reliability40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional account team sees overwritten edits, duplicate contacts, and stale opt-out preferences after synchronization retries.
Setup prerequisites
- Create a local CRM double and synthetic contact records for two organizations; no real personal data or CRM credentials.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Respect bounded retry delays.
- Keep the current cursor until a successful page.
- Distinguish terminal authentication failure from throttling.
Implementation constraints
- Use a mock clock and fixed retry ceiling.
Verification to include
- Recover from one rate-limited response.
- Exhaust retries without advancing the cursor.
Deliverables
- Rate-limit handling.
Rollout and recovery
Pause the organization sync after exhaustion; resume from its saved cursor.
Value of the work
For the engineer: Practice sync cursors, conflict policies, privacy boundaries, and replay.
For the team: Provide predictable customer-data synchronization with inspectable conflicts.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.