Skip to main content
Every request that starts work takes a requestId. It lets you retry the request without doing the work twice.

Choose a requestId

A requestId is a string of 1 to 128 characters that you choose. Use a new one for each new request.

Retry a request

If a request fails or times out, send it again with the same requestId and the same body. The work runs once, and the retry returns the same job or resource as the original request, in its current state. A request that fails validation with 422 doesn’t claim its requestId. Fix the body and send it again with the same one.

Conflicts

A retry that can’t return the original result fails with 409 CONFLICT. The message says which case applies.

Uploads

Saving an upload is safe to repeat, even with a new requestId:
  • patterns/upload with the same uploadId returns the same pattern.
  • references/create with the same uploadId returns the same reference.
Neither call makes a duplicate. If the pattern or reference has been deleted, the call returns 404. An upload can be saved as a pattern or as a reference, not both. To use a file both ways, upload it twice.

Feedback

feedback/create takes a requestId, but a retry after an error can send the report twice.

Checkouts

checkouts/create has one exception to running once. If the first request was cut off while it was starting, a retry can leave one extra unpaid checkout.