When something goes wrong in CloudM Continuity, error messages provide the information you need to diagnose and resolve the issue. This article explains where to find error details, how to read them, and what the most common error patterns mean.
Where errors appear
| Location | What it shows | When to use |
|---|---|---|
| User detail panel | Error message and error code for a specific user's failed sync | When investigating why a particular user's sync failed |
| Audit logs | All error events across the system, with severity levels, timestamps, and messages | When looking for patterns, investigating multiple failures, or reviewing historical issues |
| Connection validation | Specific error messages when a connection test fails | When setting up or troubleshooting a Microsoft 365 or Google Workspace connection |
Reading an error message
Error messages in CloudM Continuity typically include two parts:
| Part | Description | Example |
|---|---|---|
| Error message | A human-readable description of what went wrong | "Token expired" |
| Error code | A reference code for support purposes | ERR_TOKEN_001 |
The error message tells you what happened. The error code is useful when contacting support, as it allows them to identify the exact issue quickly.
Severity levels
In the audit logs, every event has a severity level that helps you prioritise:
| Severity | Meaning | Action needed |
|---|---|---|
| Information | Normal, successful operation | No action needed |
| Warning | Something may need attention but is not a failure | Review when convenient — may indicate an emerging issue |
| Error | A failure that requires investigation | Investigate promptly to restore normal operations |
You can filter the audit logs by Severity: Error to quickly find all issues that need attention. See Searching and Filtering Logs for filter guidance.
Common error patterns
| Error pattern | Likely cause | Where to start |
|---|---|---|
| Same error across all users | Connection-level issue (expired credentials, revoked permissions) | Troubleshooting Connection Issues |
| Error for a single user | User-specific issue (deleted account, provisioning failure) | Troubleshooting Sync Failures |
| Errors that appear and resolve | Temporary issue (API rate limits, brief service disruption) | Usually no action needed — monitor for recurrence |
| Provisioning errors | Google account creation issue (licence limits, permissions) | Troubleshooting User Provisioning |
Always note the error code
When contacting support, include the error code along with the affected user email and the timestamp of the failure. This allows the support team to diagnose the issue much faster.