Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reuse idempotency key should be reused when restarting sync from a 429 or 5xx response #106

Open
nicdwilson opened this issue Apr 18, 2024 · 1 comment
Open

Reuse idempotency key should be reused when restarting sync from a 429 or 5xx response #106

nicdwilson opened this issue Apr 18, 2024 · 1 comment
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: technical debt This issue/PR represents/solves technical debt of the project.

Comments

@nicdwilson
Copy link

Describe the bug

In troubleshooting 8051230-zd-a8c Square responded with the following regarding a sync interrupted by rate limiting.

We are noticing that a new idempotency_key is being used in the retry attempts. Our best practices for idempotency recommend resubmitting the request using the same idempotency_key if you receive a 429 RATE_LIMITED or 5XX HTTP response code
@nicdwilson
Copy link
Author

p1713482527612829-slack-C7U3Y3VMY

@vikrampm1 vikrampm1 added priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: technical debt This issue/PR represents/solves technical debt of the project. labels Apr 19, 2024
@a-danae a-danae mentioned this issue Apr 23, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: technical debt This issue/PR represents/solves technical debt of the project.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nicdwilson @vikrampm1