Force-Fail Fulfillment Order Submission
POST/api/fulfillment-orders/:fulfillmentOrder/force-fail-submission
Operator recovery action for a FO that is stuck submitting when retrying is not appropriate (e.g. confirmed provider/carrier outage). Transitions request_status to rejected and records the supplied reason on rejection_reason. The FO drops out of the in-flight set so it can be cancelled or re-routed.
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.
Body fields:
reason(nullable, string, max 1000) — stored onrejection_reasonfor audit. Defaults to 'Force-failed by operator (stuck dispatch).' when omitted.
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 — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
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.