Why is an execution missing from history or showing an unexpected result?
Polyosync provides execution history and result information for supported operations, including business processes, automations, workflows, and AI collaboration.
If you cannot find an execution or its result differs from what you expected, investigate the execution record before attempting the operation again.
Start with the following checks.
1. Confirm the correct workspace.
Make sure you are viewing the business workspace in which the operation was performed.
2. Review the relevant module.
An AI collaboration execution, automation run, and business process execution may be represented in their respective areas.
3. Check the date range.
If filters are available, verify that the expected execution is included.
4. Confirm that execution actually started.
A configured workflow does not necessarily produce an execution record until its trigger or starting condition occurs.
5. Review the execution status.
Where available, check whether the execution completed, failed, or remains in progress.
6. Inspect execution details.
Review recorded steps, results, error messages, and technical details where your permissions allow.
7. Compare the result with the workflow configuration.
An operation can complete technically while producing a result that differs from your business expectations.
For example, a workflow may process an input successfully but determine that no follow-up action is required.
8. Check external dependencies.
If the workflow interacts with another system, verify the corresponding action or record in that system.
Important
Do not assume that a missing visible result means the operation never occurred.
If an operation may have created a lead, sent a message, or modified an external record, verify the target system before retrying.
When to contact Support
Provide the module, workflow or process name, approximate execution time, expected result, actual result, and any available execution identifier.
This information helps Support distinguish between a missing trigger, a processing failure, a visibility issue, and an unexpected business outcome.