This topic provides answers to some frequently asked questions about how to handle alerts that are triggered when you use SchedulerX.
killed from server
In most cases, this alert is triggered if SchedulerX is configured to automatically terminate timeout jobs.
don't update progress more than 30s
The agent did not send heartbeat messages to the server for more than 30 seconds. As a result, the agent disconnected from the server. In most cases, the agent disconnects from the server if the agent is busy with publishing or the agent is overloaded. If this issue occurs because the agent is busy with publishing or the agent is restarted, you can configure SchedulerX to automatically rerun the failed jobs.