How do I understand and troubleshoot error messages in Polyosync?
Error messages in Polyosync indicate that an operation could not be completed as expected, that a request requires attention, or that a particular condition prevents an action from proceeding.
An error message does not always mean that the entire platform is unavailable.
The issue may affect a single request, AI Employee, integration, workflow, business process, or workspace operation.
How to interpret an error
Start by identifying three things:
1. What action were you attempting?
2. What error message appeared?
3. Did the operation fail completely, or did it partially complete?
These details help distinguish between configuration problems, permission restrictions, processing failures, and external service issues.
Common error categories
Authentication errors occur when an account or session cannot be authenticated.
Authorization errors occur when the current user or operation does not have permission to access a resource.
Validation errors indicate that required information is missing or does not meet the expected format.
Integration errors may involve external services, expired credentials, unavailable APIs, or rejected requests.
Execution errors occur when an automation, workflow, AI collaboration, or business process cannot complete a step.
Temporary service errors may result from network interruptions, unavailable dependencies, or processing failures.
Recommended troubleshooting procedure
1. Read the entire error message.
2. Record the affected feature and operation.
3. Note the approximate time and timezone.
4. Check whether the operation appears in the relevant execution history.
5. Review any available technical details.
6. Verify the required configuration and permissions.
7. Check whether an external integration is involved.
8. Determine whether the problem affects one operation or multiple users.
Should I retry immediately?
Not necessarily.
If the operation could send messages, create records, update external systems, or perform other business actions, verify whether the original request partially or fully completed before retrying.
When should I contact Support?
Contact Polyosync Support when the error persists, its cause remains unclear, or it affects important business operations.
Include the exact error text, affected module, expected result, actual result, approximate timestamp, and relevant execution reference.
Never include passwords, API keys, access tokens, or unnecessary confidential customer information.