Where can I find execution details, error information, and diagnostic references in Polyosync?
Diagnostic information helps identify why a Polyosync operation failed or produced an unexpected result.
The information available depends on the module, the operation, and your account permissions.
Where should I look first?
Start in the area where the operation occurred.
For example:
AI Employees
Review the relevant conversation or available activity history to identify the affected interaction.
AI Collaboration
Review available collaboration execution information, including participants, tasks, outcomes, and error details where provided.
Automations and Autonomous Workflows
Check the relevant execution history and available run information.
Business Processes
Review process execution history and the available execution details.
Integrations
Inspect the relevant connection settings and any error information associated with the failed operation.
What information is useful?
1. Execution or run reference.
2. Date and time.
3. Execution status.
4. Error message.
5. Affected operation or step.
6. Expected result.
7. Actual result.
8. Related external service, if applicable.
Are technical details always visible?
No.
The available level of detail may differ by feature and permission level.
Some diagnostic information may be available only to authorized administrators or through the support investigation process.
What if there is no execution record?
Check whether the operation was actually triggered.
An error that occurs before execution begins may not appear in the same history as a failed execution.
Should I copy all technical details into a support ticket?
Only share information relevant to the investigation.
Review technical output before submitting it, as it may contain business data, customer information, or other sensitive content.
Never share passwords, API keys, access tokens, or secret credentials.
What if I cannot access the diagnostic information?
Ask an authorized workspace administrator to review your permissions or provide the relevant reference through an approved internal process.
Do not attempt to access diagnostic information belonging to another business workspace.
When to contact Support
If the available history does not explain the problem, submit a ticket containing the affected module, timestamp, operation description, and any safe diagnostic references.
Polyosync Support can use this context to investigate further.