| Previous | Next |
| STATUS_CLOUD_FILE_REQUEST_CANCELED | STATUS_NOT_A_CLOUD_SYNC_ROOT |
STATUS_CLOUD_FILE_PROVIDER_TERMINATED
The provider process ended unexpectedly while the platform still needed it to service a Cloud Files operation. The registered sync root is not automatically proof of a bad remote account, but callbacks that depend on the dead process can no longer be completed until a healthy provider instance reconnects.
Capture crash or termination telemetry first, then restore a single provider instance that reconnects to the already registered root and reconstructs its own operation state. Avoid unregistering the root as a reflex; registration and active connection are different lifecycle stages.
Useful checks
- Collect the provider exit reason, last callback type, request key, and sync-root path.
- On startup, recover incomplete provider work and call
CfConnectSyncRootonly after callbacks are ready. - Use provider status to explain temporary unavailability while recovery is in progress.
Relevant documentation
- CfDisconnectSyncRoot describes platform cleanup after unexpected provider termination.
- CfConnectSyncRoot describes the connection that must exist before callbacks can be serviced.
Looking for a different code? Search another status or error code.