Interrupting a job scheduler
If you want to attempt to fix a running job scheduler without restarting the node, you can interrupt the job scheduler on the Requestors landing page. Interrupting a job scheduler is useful when the job scheduler stops working correctly during processing and cannot complete its run.
For example, a job scheduler runs an activity that contains a call to an external service (such as a REST endpoint, database, or email server). If that interaction with the external service stops (due to communication issues or problems with that resource), the job scheduler might not be able to finish, nor can it restart processing the activity again.
In the example above, you interrupt the job scheduler and introduce timeouts to the job scheduler activity logic.
Identify the job schedulers that are running and determine which job scheduler you want to interrupt.For more information, see Determining which job schedulers are running.
On the rightmost end of the JOBSCHEDULER_THREAD row, select the More icon (⋮), and then select Interrupt.
The Interrupt action attempts to interrupt the current activity of the Java thread. Depending on the activity implementation and depending on what the thread is doing when the interrupt attempt occurs, one of the following might happen:
- The job scheduler reacts to the interrupt attempt. The job scheduler continues with its logic or finishes immediately. The result depends on the implementation of the job scheduler activity. You do not need to restart the job scheduler; the job scheduler runs again according to its schedule (next run time).
- The job scheduler does not react to the interruption attempt. You need to restart the node where the stuck Job Scheduler job is running.