What should I do if a business process is not showing updated execution information?
If a business process is not showing the execution information you expect, begin by checking whether the relevant records are available and whether the dashboard has retrieved the latest data.
Missing or outdated information does not necessarily mean that the process itself has failed.
How can I troubleshoot the issue?
1. Sign in to your Polyosync business workspace.
2. Open Business Processes.
3. Locate the relevant process.
4. Open its Run History.
5. Use the available Refresh functionality.
6. Check whether the expected execution appears.
7. Open any available execution details to review its recorded status.
What if the execution is still missing?
Confirm that you are reviewing the correct business process and workspace.
Check whether the operation was actually started and whether any error was displayed when it was initiated.
If the process depends on an external integration, review the relevant connection where appropriate.
Could the problem be related to permissions?
Access to workspace features and operational information may depend on the user's assigned permissions.
If you believe your access is restricted, contact the appropriate workspace administrator.
What if the page fails to load?
Try refreshing the browser page and signing in again if your session has expired.
If the issue persists, note the affected process and any visible error message.
Should I repeatedly start the process to make it appear?
No.
Avoid starting multiple executions solely because the history has not updated.
A previous execution may already have initiated activities, including actions involving external systems.
What information should I provide when requesting support?
Include the affected workspace, the process name, the approximate time of the operation, the expected behavior, and any visible error messages.
Do not share passwords, API keys, access tokens, or other sensitive credentials.
Polyosync's Support Center can be used to request assistance when an execution history or monitoring issue cannot be resolved through the available interface.
Reviewing the available records and collecting relevant diagnostic information helps make troubleshooting more effective.