Retry Fulfillment Order Submission
POST/api/fulfillment-orders/:fulfillmentOrder/retry-submission
Operator recovery action for a FO that is stuck submitting — i.e. request_status=submitting for longer than the stuck threshold (config('fulfillment.stuck_submitting_threshold_minutes'), default 15) without the provider confirming. Resets request_status back to unsubmitted and clears submitted_at, so the operator (or the dispatcher) can re-attempt the hand-off.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The FO detail/list payloads expose is_stuck_submitting (boolean) so the UI can surface the amber 'stuck dispatch' banner that drives this action.
Mutability gate. Allowed ONLY when request_status=submitting AND the FO is not terminal (status not closed/cancelled). Any other state returns 409.
No request body.
Required permission: fulfillment_orders.submit (Fulfillment Orders → Submit & sync) and fulfillment_orders.index (Fulfillment Orders → View). A token also needs its orders scope; the owner needs these role permissions.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Conflict
Response Headers
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.