| Previous | Next |
| STATUS_CLOUD_FILE_PROPERTY_LOCK_CONFLICT | STATUS_CLOUD_FILE_PROVIDER_TERMINATED |
STATUS_CLOUD_FILE_REQUEST_CANCELED
This status is more specific than a generic unsuccessful operation: the user canceled the current Cloud Files request. For hydration, the platform documents cancellation reasons such as an expired request timer or explicit termination of an app-initiated download by the user.
Cancel the work associated with this request without corrupting adjacent transfers. A fetch can have overlapping or remaining required ranges, so cleanup must be keyed to the actual request and range rather than to the entire file. Do not automatically restart user-canceled work without a new explicit request.
Useful checks
- Record the cancellation flags, request key, file identity, and required byte range.
- Differentiate a timeout from an explicit user abort when deciding what feedback to show.
- Keep completed valid ranges and discard only work that belongs to the canceled request.
Relevant documentation
- CF_CALLBACK_PARAMETERS documents cancellation flags and partial-range behavior.
- CloudMirror sample is useful for tracing the provider callback and hydration flow, but is not production sync-engine code.
Looking for a different code? Search another status or error code.