| Previous | Next |
| STATUS_INVALID_WEIGHT | STATUS_NO_RANGES_PROCESSED |
STATUS_REQUEST_PAUSED
The operation is suspended rather than completed
STATUS_REQUEST_PAUSED indicates that processing stopped at a resumable point. A component may pause work while waiting for policy, user input, resource availability, transport recovery, or coordination with another request. Treating it as a permanent failure can cause duplicate work or premature cleanup.
How callers should react
- Determine whether the API documents a resume, retry, cancellation, or completion callback.
- Keep request-owned buffers and context valid until the operation is resumed or definitively cancelled.
- Avoid submitting an identical request unless the contract explicitly permits retries.
- Log the request identifier and state transition that caused the pause.
Debugging direction
Trace the component that changed the request state and identify the condition required to leave the paused state. If no resume path occurs, inspect lost notifications, cancelled worker items, resource starvation, or a state-machine transition that was skipped after an error.
References
Looking for a different code? Search another status or error code.