Common alerts in SchedulerX and how to resolve them.
What does "killed from server" mean?
In most cases, SchedulerX terminated the job because it exceeded the configured timeout threshold. This alert appears when automatic timeout termination is enabled for the job.
To resolve this alert:
Open the SchedulerX console and check the timeout settings for the affected job.
Determine whether the job genuinely needs more time or is stuck:
Job needs more time: Increase the timeout value to accommodate the expected execution duration.
Job is stuck: Investigate the root cause before raising the timeout limit. Common causes include downstream service latency, database lock contention, and resource exhaustion (CPU or memory).
Note: Raising the timeout limit without investigating the root cause may mask underlying performance issues.
What does "don't update progress more than 30s" mean?
The SchedulerX agent stopped sending heartbeat messages to the server for more than 30 seconds. The server treated the agent as disconnected.
Common causes:
| Cause | Description |
|---|---|
| Deployment or restart | The agent is temporarily unavailable during a rolling update or restart. |
| Agent overload | High CPU or memory usage on the agent machine prevents timely heartbeat delivery. |
To resolve this alert:
Check the agent machine's resource usage (CPU, memory, network) at the time the alert fired.
If the disconnection was caused by a deployment or restart, configure SchedulerX to automatically rerun failed jobs so they recover without manual intervention.
If the agent is consistently overloaded, scale the agent machine's resources or distribute workloads across additional agents.