Summary
In some environments, scheduled executions fail repeatedly due to an inconsistent execution scheduler state. The issue cannot be resolved by restarting services or retrying executions. The reliable resolution is to delete the affected execution scheduler and recreate it from scratch.
Symptoms
- Scheduled jobs do not start at the expected time.
- Manual execution works, but automated scheduling consistently fails.
- Editing the scheduling results to an Internal Server Error toast.
Root Cause
The execution scheduler configuration becomes corrupted or out of sync with the underlying system state. This can happen after:
- Tenant downtime when the execution is scheduled.
Once corrupted, the scheduler is unable to correctly register or trigger executions, and it does not self-heal.
Impact
- Automated processes are not executed, leading to delayed or missing data processing.
- Increased operational overhead due to manual execution or repeated troubleshooting.
- Potential downstream impact on reporting, integrations, or customer-facing features relying on scheduled jobs.
Workarounds
The recommended and proven workaround is to delete and recreate the execution scheduler.
Steps:
- Identify the affected execution scheduler.
- Delete the execution scheduler configuration from the system.
- Recreate a new execution scheduler from scratch.
- Verify that executions are triggered correctly according to the schedule.