Instance Observer alerts - How to identify and troubleshoot scheduler overload alertSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Scheduler is overloaded or stuck due to long-running jobs, which can significantly impact the performance and efficiency of the system. This issue can arise when jobs are not properly managed or terminated, leading to resource exhaustion and system slowdown. To resolve this, it is essential to identify and address the root cause of the long-running jobs, such as inefficient code or inadequate resource allocation. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any release of the Instance Observer can be used for diagnosis Instructions<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The issue seems to be caused by the schedulers being overloaded on the node due to long running jobs, which can significantly impact the overall performance and efficiency of the system. This overload can lead to delayed job execution, increased response times, and potential system crashes if not addressed promptly. How to identify scheduler overload: Go to Instance Observer -> Click on "Performance" Tab. -> Click on "Schedulers".Select the Instance name. Provide a duration under "Date Range". Click "Get Snapshot".Scroll down to "Scheduler Queue Length". This graph illustrates the count of claimed scheduled jobs in each application node within the memory scheduler queue. Keep in mind that this does not account for scheduled jobs currently being executed on a worker thread in the application node.If the graph illustrates a spike as shown in the screenshot, it indicates a potential issue where there may be an influx of jobs for certain jobs that have been running for an extended period of time, thereby holding onto the worker thread. This can lead to a buildup of jobs in the scheduler queue, causing delays in job execution and potentially impacting the overall performance of the system. It is essential to investigate and address this issue promptly to prevent further delays and ensure efficient system operation. How to provide relief from scheduler overload: Once the scheduler overload is identified, go to the "Transactions" tab located next to the Scheduler queue length graph. Click on "Active Transactions" to be redirected to the instance, where you can view the current active transactions and their statuses.Alternatively, you can access the same page by navigating to the instance, clicking on Filter Navigator, and searching for "System Diagnostics" -> "Active Transactions (All Nodes)". This will provide you with a comprehensive list of all active transactions across all nodes in the system.Identify the job name that is causing the influx or running for an extended period, holding the worker thread. It is crucial to kill this job to provide relief and prevent further delays in job execution.To temporarily disable the job, navigate to Filter Navigator -> System Scheduler -> Scheduled Jobs -> Scheduled Jobs. Search for the job name and click on the record to access its settings.By changing the "Trigger Type" to "On Demand", the job will not run automatically, allowing you to manually control when it executes. This can be a useful temporary measure to prevent the job from overloading the scheduler.Additionally, ensure that any Business Rules or Script Includes that are triggering this job are also disabled to prevent them from inadvertently starting the job and causing further scheduler overload.