How can we help?

If a scheduled automation fails, Polyosync provides execution information that can help businesses understand what happened and investigate the problem. An automation may encounter an error for several reasons, including unavailable integrations, invalid configuration, missing permissions, execution limits, or failures in a required external service. Does Polyosync record automation executions? Yes. Polyosync includes automation execution records and reporting capabilities. These help businesses distinguish successful executions from unsuccessful ones and review the available results. What should I check if an automation fails? Start by reviewing the automation's execution information. Check whether: - The automation is active and correctly configured. - The assigned internal AI Employee is active. - Required integrations and tools are available. - The automation has the necessary access permissions. - Any configured conditions or execution limits are preventing progress. - An external service has returned an error. Will Polyosync automatically retry every failed automation? Not necessarily. Retry and recovery behavior depends on the execution path and the type of failure. Businesses should not assume that every unsuccessful action will automatically be repeated. Can I run the automation again? Where the automation and your access permissions allow it, you can initiate another execution after addressing the underlying issue. Why does execution history matter? An automated process should not become an invisible process. Execution records help organizations investigate problems, review outcomes, and improve the reliability of recurring operations. Polyosync combines automation execution with operational visibility so businesses can maintain oversight of their automated activities.