🔧 Scheduler Troubleshooting¶
This guide helps you diagnose and resolve common issues with the EasyTask Scheduler.
🐛 Common Issues and Solutions¶
| # | Issue | Possible Cause | Solution |
|---|---|---|---|
| 1 | Scheduler instance not starting | Database or message broker not connected | Check database connection settings and message broker connectivity in the configuration. Verify both services are running and accessible. |
| 2 | Task not getting triggered | Task definition, timezone, or dependency issues | Verify the task definition is correct. Check that the timezone setting matches the intended schedule. Confirm that all upstream dependencies have completed successfully. |
| 3 | Task triggered but not submitted to agent | Agent queue issue or agent in breached list | Check that the target agent is online and connected. Verify the agent is not in the breached agents list. Check the agent's queue for pending tasks and confirm the agent is registered with the scheduler. |
| 4 | Task submitted but no status updates | Scheduler status subscription issue | Check the scheduler health from the Dashboard. If the status subscription thread is not responding, restart the scheduler instance. |
| 5 | Task dependencies not being met | Upstream task failure or configuration error | Enable debug mode from the Scheduler Dashboard to see detailed dependency evaluation logs. Identify which upstream task is blocking execution and investigate its status. |
| 6 | Retry not working | Incorrect retry configuration | Review the task's retry configuration. Verify retry_attempts is set to a value greater than 0 and max_run_time is appropriate for the task. |
| 7 | Scheduler shows degraded status | One or more threads not alive | Check the Thread Monitor on the Scheduler Dashboard. Identify which threads are dead and consider restarting the scheduler. |
📋 Diagnostic Steps¶
Check Scheduler Health¶
- Navigate to the Scheduler Dashboard (
/scheduler) and check the overall status. - Verify all 7 threads show as "Alive" in the Thread Monitor.
- Check the health check age — if it's stale, the scheduler may be unresponsive.
Check Recent Logs¶
- Use the live log viewer on the Scheduler Dashboard to check for errors.
- For on-prem deployments, check the scheduler container logs:
Use the system service manager to view recent scheduler logs.
Check Dependent Services¶
- Verify the database is running and accessible.
- Verify the message broker is running and accessible.
- Verify the identity provider is running (for authenticated operations).
Check Task Definitions¶
- Verify the task has an active schedule and is enabled.
- Check that
day_of_weekandtrigger_timesare correctly configured. - Confirm the task's assigned instance matches the running scheduler instance.
- Check that the assigned calendar does not mark the current day as a holiday.
🔄 Restart Procedures¶
Via Web UI¶
Go to the Scheduler Dashboard (/scheduler) and use the Container Management section to restart the scheduler.
Via Command Line (On-Prem)¶
For on-prem deployments, use the system service manager or container commands to restart the scheduler.
Frequently Asked Questions¶
Q: The scheduler is running but tasks are not triggering. What should I check? A: First, verify the task is enabled and has a valid schedule. Check the timezone setting — if it doesn't match the intended schedule, triggers may occur at unexpected times. If the task has dependencies, confirm all upstream tasks have completed. Enable debug mode from the Dashboard to see detailed trigger evaluation logs.
Q: The scheduler shows as degraded. What does this mean? A: A degraded status means one or more internal threads are not alive. Check the Thread Monitor on the Scheduler Dashboard to identify which threads are affected. A restart typically resolves this issue.
Q: How do I enable debug mode for troubleshooting?
A: Go to the Scheduler Dashboard (/scheduler) and click "Debug On" in the Event Actions card. Debug mode provides detailed logging for trigger evaluation, dependency checks, and task dispatch. Remember to turn it off ("Debug Off") after troubleshooting.
Q: A task was triggered but the agent never received it. What's wrong? A: Check that the target agent is online and connected to the scheduler. Verify the agent is not in the breached agents list. Check the agent's queue for backlogs. If the agent is offline, the task will remain in a pending state until the agent reconnects.