| Previous | Next |
| ERROR_CLOUD_FILE_PINNED | ERROR_CLOUD_FILE_PROPERTY_CORRUPT |
ERROR_CLOUD_FILE_REQUEST_ABORTED
The operation ended because its processing was aborted
ERROR_CLOUD_FILE_REQUEST_ABORTED indicates that an in-progress cloud operation stopped before producing a normal result. This can follow provider shutdown, superseding work, loss of a required remote session, or an internal decision that the request can no longer be completed. It is not the same as the explicit user-cancel status.
Trace the request from callback receipt through transfer-key completion and record the component that initiated the abort. Ensure partial data or placeholder enumeration is completed with the correct failure status and that provider state is released exactly once. A retry should use a fresh request context and revalidate FileIdentity and remote version; reusing an obsolete transfer key after abort can corrupt request accounting.
What to inspect
- Log the abort initiator and the last completed offset or enumeration position.
- Release buffers, handles, and remote requests on every abort path.
- Create a new request context for retry and revalidate placeholder identity.
References
- Microsoft: cancel and data-fetch callback types
- Microsoft: operation keys and completion parameters
- Microsoft: callbacks during provider disconnect
Looking for a different code? Search another status or error code.