| Previous | Next |
| STATUS_CLOUD_FILE_INSUFFICIENT_RESOURCES | STATUS_CLOUD_FILE_UNSUCCESSFUL |
STATUS_CLOUD_FILE_NETWORK_UNAVAILABLE
This status belongs to the provider's remote transport path, not to the local placeholder format. The sync root can remain registered and its existing full or pinned files can still be usable offline while a request requiring remote enumeration, hydration, upload, or validation cannot proceed.
Record whether the failed operation was a fetch, upload, namespace population, or validation request, then apply the provider's retry and offline policy. Do not mark a locally changed file in sync simply because the platform can still read metadata while the network is unavailable.
Useful checks
- Separate DNS, proxy, TLS, captive-network, and remote-service failures in provider telemetry.
- Keep partial or queued work associated with its file identity and request context for a later resume.
- Expose a provider status rather than presenting this as a malformed local placeholder.
Relevant documentation
- Build a Cloud Sync Engine distinguishes provider sync responsibilities from placeholder management.
- CfReportSyncStatus explains how a provider can report meaningful failure status to the platform.
Looking for a different code? Search another status or error code.