| Previous | Next |
| STATUS_CLOUD_FILE_PINNED | STATUS_CLOUD_FILE_PROPERTY_CORRUPT |
STATUS_CLOUD_FILE_REQUEST_ABORTED
This is a per-request terminal outcome. It does not by itself identify a corrupt sync root, a bad remote object, or an invalid provider registration. The provider needs the request context to determine whether the work was interrupted by cancellation, shutdown, timeout, a superseding operation, or its own controlled abort path.
Preserve the callback's request key, transfer key, file identity, and byte range. Do not assume the entire file operation vanished: a cancellation can apply to only a subset of a fetch range while other pending I/O still needs data.
Useful checks
- Handle cancellation before releasing buffers or deleting state shared by overlapping requests.
- Record whether the provider was shutting down or a higher-level operation superseded this request.
- Resume only through a new platform request or a documented explicit hydration flow.
Relevant documentation
- CF_CALLBACK_PARAMETERS explains cancellation ranges and outstanding fetch work.
- CfConnectSyncRoot describes the callback connection lifecycle.
Looking for a different code? Search another status or error code.