What should I do if a scheduled automation does not run?
If a scheduled automation does not run at the expected time, first verify that it is active, correctly configured, and eligible for execution.
Polyosync supports scheduled automations, but successful execution depends on the automation's status, scheduling configuration, assigned AI Employee, and applicable platform requirements.
What should I check first?
1. Confirm that the automation is active rather than saved as a draft or otherwise inactive.
2. Review its scheduling configuration, including the selected time, recurrence, and time zone.
3. Verify that the assigned internal AI Employee is active and accessible within the business workspace.
4. Check whether the required automation functionality is available under your business account.
5. Review the available execution history to determine whether the automation started and encountered an error.
6. Check whether required integrations, tools, or permissions have changed.
Could the time zone cause the problem?
Yes. A mismatch between the intended business time zone and the configured scheduling time zone can make an automation appear to run earlier or later than expected.
Review the time-zone settings, particularly when operating across different countries or during daylight saving time changes.
Do I need to leave Polyosync open in my browser?
No. Scheduled automation execution is handled by the platform's backend infrastructure.
Keeping a browser tab open is not required for an active, correctly configured schedule to execute.
What if the automation still does not run?
Review its execution information and contact Polyosync Support if the issue remains unresolved.
Provide the automation name, expected execution time, configured time zone, and any relevant error details.
Scheduled automations help businesses maintain recurring operational routines, while execution visibility makes it easier to investigate interruptions when they occur.