--- sourceDocument: Yokohama ServiceNow AI Platform Administration sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/platform-administration Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Understand your Scheduled Jobs dashboard # Understand your Scheduled Jobs dashboard {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Understand your Scheduled Jobs dashboard The Scheduled Jobs dashboard in ServiceNow Yokohama provides key health metrics and insights into the status and performance of scheduled jobs on your instance. Accessible viaAll \> System Diagnostics \> Scheduled Jobs Dashboard, it helps you monitor job execution, identify issues, and manage job states effectively. Show full answer Show less ## Key Features * **Stuck Jobs:** Displays jobs assigned to non-existent nodes, typically after cloning instances. These jobs can be deleted permanently or recovered to clear node assignment and allow normal execution. * **Permanent Error Jobs:** Shows jobs in a Permanent Error state, often due to upgrades or manual state changes. You can delete or recover these jobs to reset their state to Ready. * **Pending Jobs:** Lists jobs scheduled to run soon. * **Running Jobs:** Shows jobs currently executing. * **Jobs Classification (optional):** Allows grouping of jobs by filter conditions to collect completion history, configurable in the Job Classification Rules table. * **Total Execution Count:** Graph showing the number of job executions over the last 24 hours (data available for up to 7 days), sourced from `sysschedulerjobhistory`. Clicking on graph data displays detailed job history grouped by classification. * **Average Lateness:** Graph showing average lateness in milliseconds of scheduled jobs over the last 24 hours (up to 7 days). Lateness indicates delay relative to scheduled run time. * **Scheduled Job Trends:** Lists completed jobs grouped by classification, showing execution count and processing times over the last 24 hours. ## Practical Use and Benefits ServiceNow customers can use this dashboard to: * Identify and clean up stuck or permanently errored jobs to maintain healthy job scheduling. * Monitor pending and running jobs to track job execution status in real-time. * Analyze execution trends and lateness to optimize job scheduling and system performance. * Classify jobs based on custom rules to better understand job completion patterns. ## Details on Important Fields and Metrics * **Stuck and Permanent Error Jobs:** Data comes from `systrigger`, showing job node assignments and state, enabling cleanup actions. * **Lateness Calculation:** If the next action time is in the past, lateness equals current time minus scheduled time; if in the future, lateness is zero. * **Scheduled Job Trends Fields:** * **Job Classification:** Groups jobs by name and trigger type. * **Priority:** Processing priority where lower numbers indicate higher priority. * **Execution Count:** Number of executions in the timeframe. * **Average and Total Processing Time:** Time in seconds spent processing jobs. Visit scheduler dashboard to learn about key health metrics and insights of scheduled jobs. Navigate to AllSystem DiagnosticsScheduled Jobs Dashboard. The following cards show up on the dashboard{#scheduled-jobs-dashboard__table_wwg_yvf_nxb__entry__2} | Field | Description | |-|-| | Stuck Jobs | The scheduled jobs that are pinned to a non-existent node show up here. If a scheduled job is assigned to run on a non-existent node and is a parent job that doesn't have Startup as the Trigger Type, it is classified under Stuck Jobs. The System ID column states the node that the job was assigned to run. One of the reasons of a job being classified as Stuck Jobs is if an instance was cloned from another instance and now there are jobs pinned to run on the old instance's nodes. You can take the following actions on the stuck jobs: * You can delete it to remove the job from sys_trigger permanently. * You can recover these jobs which clears theSystem ID column data and allows it to run again based on its Next Action time. {#scheduled-jobs-dashboard__ul_d2k_g2j_1cc} | | Permanent Error Jobs | The scheduled jobs which have a State of Permanent Error show up here. If you have upgraded from a pre-Utah version to a more recent version, a fix script is executed and it sets the scheduled jobs to Permanent Error state if the job was a parent job or a standalone job and picked up to run on a specific node that no longer exists. You can also set the job state to Permanent Error manually. You can take the following actions on the permanent error jobs: * You can delete it to remove the job from sys_trigger permanently. * You can recover these jobs which set the state back to Ready. It can again run based on its Next Action time. {#scheduled-jobs-dashboard__ul_zds_fdj_1cc} | | Pending Jobs | Jobs that are to be executed soon. | | Running Jobs | Jobs that are actively running. | | Jobs Classification (optional) | Optional way to group certain jobs based on filter conditions to collect job completion history by the defined group/classification. You can set up these classifications in the Job Classification Rules table. The default classification is TriggerType.JobName. | | Total Execution Count | Graphical representation of the total number of scheduled job executions on your instance over a period of time. The default time period is last 24 hours. You can view the data only from last 7 days. The data originate from the sys_scheduler_job_history table. Note: When you click on an execution count in the graph, the Scheduled Job History list shows up. The list of jobs have been grouped using Jobs Classification concept with Trigger Type as either Run Once or Recurring. | | Average Lateness | Graphical representation of the average lateness in milliseconds of all scheduled jobs on your instance over a period of time. The default time period is last 24 hours. You can view the data only from last 7 days. The data originates from the sys_scheduler_job_history table. Note: When you click on a lateness average data in the graph, the Scheduled Job History list shows up. The list of jobs have been grouped using Jobs Classification concept with Trigger Type as either Run Once or Recurring. | | Scheduled Job Trends | List of completed jobs grouped by Job Classification concept. The default time period is last 24 hours. You can view the data only from last 7 days. The data originate from the sys_scheduler_job_history table. | [ ] {#scheduled-jobs-dashboard__table_wwg_yvf_nxb} Note: For both Stuck Jobs and Permanent Error Jobs tiles, the data and columns originate from the sys_trigger table. Both the tiles are used to cleanup jobs and keep the scheduled jobs in a positive state. Select the required tile to see the list view of the jobs. The Lateness column on both the lists refers to how late the job is based on the time it was supposed to run. If Next Action is in the past, the lateness is calculated as the current time minus the next action time. For example, if the job was scheduled to run two minutes ago, then lateness is two minutes. If the job is scheduled to run in the future, then the lateness is 0. ## Scheduled Job Trends {#scheduled-jobs-dashboard__section_uwv_tk1_4xb} This table provides details on the history of completed jobs by classifications. Default view provides the data for last 24 hours. {#scheduled-jobs-dashboard__table_rdk_cfq_hyb__entry__2} | Field | Description | |-|-| | Job Classification | Provides a way of grouping similar type of jobs based on job name, trigger type (recurring, run once, etc.). | | Priority | Priority at which the jobs are processed. Note: The lower the number, the higher is the priority. For example, priority of 10 is higher than 100. | | Execution Count | Number of times the job has been executed within a timeframe. | | Average Processing Time(s) | Average time in seconds needed to process the jobs. | | Total Processing Time(s) | Total time in seconds needed to process the jobs. | [ ] {#scheduled-jobs-dashboard__table_rdk_cfq_hyb} *[\>]: and then