Polyosync Help Center

How can we help?

Browse help articles or contact our support team.

Request Support

Why is my business process failing in Polyosync?

A business process in Polyosync may fail for several reasons, including configuration problems, missing or invalid input data, unavailable integrations, permission restrictions, or errors encountered during execution. A failed execution does not necessarily mean that the entire process configuration is incorrect. The problem may be limited to a particular activity or dependency. How to investigate a failed process: 1. Sign in to your Polyosync business workspace. 2. Navigate to Business Processes. 3. Locate the affected process. 4. Open Run History. 5. Select the failed execution. 6. Review its recorded status, error information, execution events, and results. 7. Open the available technical details if additional diagnostic information is needed. Common causes of execution failures: - Missing required information. - Incorrect process configuration. - Invalid or unexpected input values. - External integration failures. - Insufficient permissions. - Temporary service or dependency problems. - Errors encountered while processing a particular activity. How can I determine which cause applies? Begin with the recorded error information. If the execution details identify a particular problem, investigate that issue before changing unrelated settings. Review the process configuration and confirm that the required information is available. If the process depends on an external service, verify that the connection is operational and that the required permissions remain valid. Should I immediately restart the process? Not necessarily. Some failed executions may have completed earlier activities before encountering an error. Restarting without reviewing the previous outcome could repeat actions such as creating records or sending communications. What if the error remains unresolved? Contact Polyosync Support and provide the process name, approximate execution time, relevant error message, and a description of the expected behavior. Never include passwords, API keys, or access tokens in a support request. Polyosync provides execution records and diagnostic information to help businesses investigate process failures and determine appropriate corrective actions.