--- sourceDocument: Australia Impact sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/impact Release : - australia ft:locale : - en-US ft:publication_title : - Australia Impact ft:clusterId : - ipact bundleId : - ipact --- # Scheduler performance metrics # Scheduler performance metrics {#ariaid-title1} * Release version: Australia * * Updated May 20, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Scheduler performance metrics Scheduler performance metrics provide a snapshot of how scheduled jobs are handled within the ServiceNow AI Platform®. These metrics help monitor the efficiency and health of job processing across application nodes, ensuring timely execution and identifying potential performance bottlenecks. Show full answer Show less ## Key Metrics * **Completed Scheduled Jobs:** Tracks the number of scheduled jobs completed per node. These jobs include scheduled reports, script executions, SLA or workflow timers, email sending, event processing, and asynchronous business rules that run on the scheduled job queue. A sudden increase in job counts may overwhelm processing capacity, causing lag. * **Scheduler Mean Queue Age:** Measures the average time unprocessed jobs spend in the in-memory scheduler queue after being claimed by a node. A high mean queue age suggests the node is struggling to process jobs promptly, possibly due to long-running jobs occupying worker threads. Since the New York release, nodes can return unprocessed jobs to the systrigger table for other nodes to claim if they cannot process them timely. * **Scheduler Queue Length:** Indicates the number of claimed scheduled jobs waiting in each node's in-memory queue, excluding currently executing jobs. Sustained high queue length and increasing queue age on a node can signal processing issues. If multiple nodes exhibit this behavior, the instance may be overloaded. ## Practical Guidance for Customers * Monitor the volume of completed scheduled jobs to detect unexpected spikes that may impact system responsiveness. * Investigate long-running scheduled jobs to optimize their frequency, performance, or stagger execution times to reduce queue age and avoid blocking worker threads. * Track scheduler queue lengths and mean queue age per node to identify and address nodes struggling to keep up with job processing. * Utilize the job return functionality (available from New York release onwards) to enable load balancing of unprocessed jobs across nodes. * Coordinate these metrics with related performance data such as job details, node health, and database performance to comprehensively address scheduling issues. The metrics provide the Schedulers performance snapshot within the ServiceNow AI Platform®. ## Completed Scheduled Jobs {#io-schedulers-perf-metrics__section_a5c_5lx_hjc} The number of scheduled jobs completed per node. There are many types of scheduled jobs. They could be scheduled reports, scheduled script executions, one-time jobs like SLA or Workflow Timers, or repeating jobs like Email Sender or Event Processor. In addition to what you might think of as traditional scheduled "jobs" there is also a couple special case of operations that run on the scheduled job queue called, Asynchronous business rules. These can be work that was triggered from the UI or an integration but runs as a scheduled job to achieve asynchronous behavior. Typical examples of Asynchronous business rules are Discovery Sensors or perhaps a job that iterates over a large number of child records, making so many updates that it would not be a good user experience to have to wait for them all to complete. Note: * When scheduled job counts suddenly shoot up this can be concerning as it may overwhelm processing and cause lag. * This should be considered together with other job metrics like the scheduler age, scheduler queue length, and pending jobs counts. {#io-schedulers-perf-metrics__ul_ov1_xlx_hjc} ## Scheduler mean queue age {#io-schedulers-perf-metrics__section_uwn_zlx_hjc} The average age of all unprocessed jobs in an application node in memory scheduler queue (i.e., the delta between the job being claimed by the node or placed in the queue and the point at which metrics were collected). Note that this does not include time the job spent pending in the sys_trigger table between its 'Next Action' time (that is, when it should have run) and when it was claimed. A large scheduler mean queue age can indicate that an application node is struggling to process claimed jobs (that is, those in its in memory queue) in a timely manner. Note: Check to see if the majority of worker threads on the corresponding node are busy executing long running scheduled jobs --- in this scenario long running jobs should be investigated to reduce frequency/improve performance/stagger execution. In New York and later a node which is unable to process claimed jobs can send these jobs back to the sys_trigger table to be claimed by other nodes. Check whether this functionality is working as expected ## Scheduler queue length {#io-schedulers-perf-metrics__section_xg4_kmx_hjc} The number of claimed scheduled jobs in each application nodes in memory scheduler queue. Note that this does not include scheduled jobs which are currently executing on a worker thread on the application node. It is common for application nodes to claim multiple jobs at once and therefore have a significant scheduler queue length at any point in time. If a single node has significant queue length for a sustained period (that is, more than 60 minutes), where queue length does not drop down to 0 and scheduler age is increasing, this may indicate the node has an issue processing scheduled jobs. If multiple nodes see similar issues it may indicate either all nodes are having issues processing scheduled jobs or the instance is simply overwhelmed by scheduled jobs. Note: * Check scheduled jobs executing on application nodes to determine type or source. * Address performance or scheduling of jobs as necessary to prevent them overloading worker threads. {#io-schedulers-perf-metrics__ul_yhq_44x_hjc} **Related reference** * [Anomaly insights](https://servicenow-prod.fluidtopics.net/4_QeeoMptTF3e9qrg4XWwg "The reference topic gives additional information for anomaly charts.") * [Feature availability based on package](https://servicenow-prod.fluidtopics.net/P9qjLGc3vCF_cOO3tzGPpA "The table outlines the access permissions for Performance Analytics features across production and sub production instances.") * [Auriga Intelligent Alert report](https://servicenow-prod.fluidtopics.net/nQSJ7KPMZhRA30JC0WUapA "Auriga Intelligent Alert is an advanced multivariate machine learning (ML) model that learns from historical issues on your instance to provide real-time insight. Auriga monitors your performance metrics to deliver notifications of noteworthy events or deviations from anticipated data patterns.") * [Transaction or response metrics](https://servicenow-prod.fluidtopics.net/zO1ipLkzD4Ui4sKzEQk4bg "The metrics provide a performance snapshot of classic UI transactions within the ServiceNow AI Platform.") * [Database performance metrics](https://servicenow-prod.fluidtopics.net/BR2AN_h8wOEd8ZtqZdLf4A "The metrics provide the database performance snapshot within the ServiceNow AI Platform.") * [Semaphores performance metrics](https://servicenow-prod.fluidtopics.net/Kk9mReT78mDBECtqFl7MWQ "The metrics provide the key performance indicators calculated at the instance level for the selected duration.") * [Event queues performance metrics](https://servicenow-prod.fluidtopics.net/gJEASVHBrJdFQHIBS8345w "The metrics provide the event performance snapshot within the ServiceNow AI Platform.") * [ECC Queue performance metrics](https://servicenow-prod.fluidtopics.net/RGxMtNOGgtVY6Q5itGNFaQ "The metrics provide the ECC Queue performance snapshot within the ServiceNow AI Platform.") * [Email performance metrics](https://servicenow-prod.fluidtopics.net/bogAIEvZQM6EVgHuNANWkw "The metrics provide the Email performance snapshot within the ServiceNow AI Platform.") * [Job details performance metrics](https://servicenow-prod.fluidtopics.net/zU5pCERdUDwYINhrEtEmVw "The metrics provide the job details performance snapshot within the ServiceNow AI Platform.") * [Node health performance metrics](https://servicenow-prod.fluidtopics.net/Ym_5QZb7HaUEXusPO0FNVA "The metrics provide the node health performance snapshot within the ServiceNow AI Platform.") * [Host health performance metrics](https://servicenow-prod.fluidtopics.net/BPg~fi7mWtO2QDvoJtmlbw "The metrics provide the host health performance snapshot within the ServiceNow AI Platform.") * [Standby replication Lag](https://servicenow-prod.fluidtopics.net/~bnGXSPhIInh_QygPmu8lA "A read replica is a copy of the primary DB that reflects changes to the primary in almost real time, in normal circumstances. The lag represents the database server of the instance that is behind in seconds.") * [Pool Replication Lag](https://servicenow-prod.fluidtopics.net/GZt7jzZ4mbs0axGHLTG75w "Pool replication lag is the number of seconds that a Standby database or a read replica database lags behind the primary database.") * [Chat details performance metrics](https://servicenow-prod.fluidtopics.net/3ITlZgnjjx7hFU0jPdggHA "For the operations team to get the insights of current load across main components of AWA channel infrastructure like queues and agents, and to monitor load during events of chat spikes.") * [Cluster details performance metrics](https://servicenow-prod.fluidtopics.net/gCpPJvTx4G~JcYX9~VAIVA "The metrics provide the cluster details and Encryption status snapshot within the ServiceNow AI Platform.") * [Load balancer performance metrics](https://servicenow-prod.fluidtopics.net/U6~7lb0jujHirGTJlHHmZA "The metrics provide the load balancer performance snapshot within the ServiceNow AI Platform.") * [User information metrics](https://servicenow-prod.fluidtopics.net/tzinVKez9tWy7F1KJoK7mg "The metrics provide the user information performance snapshot within the ServiceNow AI Platform.") * [Instance Data Replication](https://servicenow-prod.fluidtopics.net/ScxZA~8x58vIrm57FTmurg "The Instance Data Replication (IDR) copies data updates from one instance, called the producer instance, to one or more other instances called the consumer instances.")