| Previous | Next |
| STATUS_CLOUD_FILE_NETWORK_UNAVAILABLE | STATUS_CLOUD_FILE_NOT_UNDER_SYNC_ROOT |
STATUS_CLOUD_FILE_UNSUCCESSFUL
This is an umbrella result, not a diagnosis. Its value is in preserving the exact operation context that should have produced a more specific reason: provider callback type, sync-root path, file identity, request key, transport result, and any provider-generated sync status.
Do not collapse all such failures into a generic retry loop. First inspect whether the provider supplied a file-level or root-level CF_SYNC_STATUS; the platform can retain that information and use it to construct a more actionable error message for a failed placeholder operation.
Useful checks
- Log the callback or operation type and all opaque keys without attempting to interpret their bytes.
- Store provider error context through the documented sync-status mechanism.
- Use the next specific result from provider telemetry to choose retry, reauthentication, repair, or conflict handling.
Relevant documentation
- CfExecute explains file-level sync status attached to provider operations.
- CfReportSyncStatus documents root-level status used when a file-level status is unavailable.
Looking for a different code? Search another status or error code.