How can we help?

A business process can encounter an error after one or more earlier activities have already completed. This means an unsuccessful final execution status does not necessarily indicate that every activity failed. For example, a process may successfully prepare information or perform an external action before encountering an error in a later operation. How to investigate a partially completed execution: 1. Navigate to Business Processes. 2. Open the affected process. 3. Select the relevant execution from Run History. 4. Review the recorded execution events. 5. Examine the available results and error information. 6. Determine which activities were completed and which remain uncertain. 7. Check relevant external systems if the process performed actions outside Polyosync. Why is partial completion important? Some operations produce changes that are not automatically reversed when a later activity fails. For example, a record may have been created in an external application before a subsequent operation encountered an error. Does Polyosync automatically reverse every completed action after a failure? Automatic reversal should not be assumed. Whether an action can be reversed depends on the operation, its configuration, and the systems involved. Should I restart the entire process? Only after reviewing the previous execution's effects. Starting another run without understanding partial completion may repeat actions or create inconsistent business data. How should I handle uncertain outcomes? Verify the relevant information in the systems involved. If the process affects critical business operations, follow your organization's established recovery procedures. Can execution history help? Yes. Recorded events, results, and errors can provide useful information about the sequence and outcome of activities. However, not every external action is necessarily represented by a separate event. Polyosync helps businesses investigate partial execution outcomes and make informed recovery decisions.