| Previous | Next |
| ERROR_CLOUD_FILE_PROPERTY_LOCK_CONFLICT | ERROR_EXTERNAL_SYSKEY_NOT_SUPPORTED |
ERROR_CLOUD_FILE_REQUEST_CANCELED
The request ended through explicit user cancellation
ERROR_CLOUD_FILE_REQUEST_CANCELED is the user-cancellation result and should be kept distinct from a provider abort, timeout, network loss, or process termination. CFAPI includes cancel callbacks for outstanding data and placeholder-fetch requests so the provider can stop remote work and release request-specific resources.
Propagate cancellation through the provider's remote request, buffer pipeline, and CfExecute completion exactly once. Record how much data was transferred and whether partially hydrated ranges remain valid. Do not convert user cancellation into authentication or generic failure in telemetry, and do not automatically restart a large operation that the user intentionally stopped. A later user retry should begin with a fresh request and current remote version.
What to inspect
- Log the original cancel event and associated transfer key.
- Stop remote I/O and release buffers without double-completing the request.
- Report cancellation separately from abort, timeout, and network failure.
References
- Microsoft: cancel-fetch callback types
- Microsoft: operation completion and transfer keys
- Microsoft: asynchronous hydration requests
Looking for a different code? Search another status or error code.