How can we help?

Contact Polyosync Support when an automation continues to fail after you have checked its configuration, permissions, integrations, and available execution information. Support is also appropriate when the cause of a failure is unclear or when a problem appears to affect multiple automations. What should I check before contacting Support? Confirm that the automation is correctly configured and active. Review the assigned AI Employee and required tool permissions. Check whether relevant integrations are connected and functioning. Examine the available execution history for errors or incomplete operations. For scheduled automations, verify the configured schedule and time zone. What information should I provide? To help the support team investigate, include: - The name of the affected automation. - A description of what you expected to happen. - What actually happened. - The approximate time of the failed execution. - Any relevant error message or execution identifier. - The affected integration, if applicable. - Whether the issue occurs consistently or intermittently. Avoid including passwords, API keys, access tokens, or other sensitive credentials in your support request. What if the automation affects an important business process? If the workflow performs business-critical activities, review the operational impact and determine whether a temporary manual process is needed while the issue is investigated. Do not repeatedly restart an automation that may have partially completed external actions without first checking for possible duplicate effects. Can Support help distinguish configuration issues from platform problems? The information you provide can help the team investigate whether the problem relates to configuration, permissions, an integration, or platform execution. Polyosync's execution records provide a useful starting point for troubleshooting, helping businesses communicate problems more clearly and reduce unnecessary investigation time.