This topic describes how to handle the alerts that you may receive when using SchedulerX.
killed from server
Alert message
The timed scheduling task in your ****** environment, namespace: default space, jobid:******, trigger instance id:******, failed at 2025-10-15 07:40:57. The task ran on machine ******. The reason may be 'killed from server'. Please monitor the task. [SchedulerX access ******.com].
Description
This alert indicates that a task was automatically purged because it timed out.
don't update progress more than 30s
Alert message
The timed scheduling task in your ****** environment, namespace: default space, jobid:******check_if_complete_BACKIP1), trigger instance id:******, failed at 2025-10-15 07:40:57. The task ran on machine ******. The reason may be 'jobInstance=*** don't update progress more than 30s, maybe worker=****** is down'. Please monitor the task. [SchedulerX access ******.com].
Description
The connection between the client and the server was lost because no heartbeat was sent for more than 30 s. This issue is typically caused by a client deployment or high load. If the issue is caused by a deployment or restart, you can configure automatic retries for failed tasks.