Resume store clone

Continues an operation that stopped with NEEDS_ATTENTION, was cut by the time budget (202) or is still IN_PROGRESS. It starts at the first step not concluded. Steps DONE or SKIPPED are not run again.

If the operation is already completed, nothing runs and the answer is 200. A step that failed with lastError.retryable: false is not retried: the answer is 200 with the operation unchanged. To fix the data of such a step, create a new clone with a new Idempotency-Key: the same key with a different body answers 409.

Access
The operation is read first with the same rules as GET /retailers/clones/{operationId}, so an unknown operation, or one from another group, answers 404. After that, the same access checks as the create route run against the stored source store (store-clone flag, caller with groupId, source store in the group, caller accesses the source store) and a failed check answers 403.

Result
The result codes are the same as the create route: 201 for an operation completed in this call, 200 when no step ran, 202 with nextAction: RESUME when the time budget ran out again, and 207 when a step is still FAILED or BLOCKED.
409 means another call is already processing the operation. Try again in a moment.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The Idempotency-Key that created the operation. It is not case sensitive.

Responses

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json