{"title":"Analyzing job queue lifecycle telemetry","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/telemetry-job-queue-lifecycle-trace/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-job-queue-lifecycle-trace, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/telemetry-job-queue-lifecycle-trace","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Analyze job queue lifecycle telemetry in Business Central to monitor queued tasks, successful runs, retries, cancellations, and entries that fail.","date":"2026-11-17","meta":{"topic":"reference"},"outline":[{"level":1,"title":"Analyzing job queue lifecycle telemetry","slug":"analyzing-job-queue-lifecycle-telemetry","at":0,"chars":20604},{"level":2,"title":"Job queue telemetry events","slug":"job-queue-telemetry-events","at":847,"chars":1750},{"level":2,"title":"Common custom dimensions to all job queue events","slug":"common-custom-dimensions-to-all-job-queue-events","at":2597,"chars":2587},{"level":2,"title":"Job queue entry enqueued","slug":"job-queue-entry-enqueued","at":5184,"chars":1591},{"level":3,"title":"General dimensions","slug":"general-dimensions","at":5488,"chars":334},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions","at":5822,"chars":953},{"level":2,"title":"Job queue entry failed to be enqueued","slug":"job-queue-entry-failed-to-be-enqueued","at":6775,"chars":640},{"level":3,"title":"General dimensions","slug":"general-dimensions-1","at":6882,"chars":338},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-1","at":7220,"chars":195},{"level":2,"title":"Job queue entry started","slug":"job-queue-entry-started","at":7415,"chars":600},{"level":3,"title":"General dimensions","slug":"general-dimensions-2","at":7487,"chars":333},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-2","at":7820,"chars":195},{"level":2,"title":"Job queue entry finished (request)","slug":"job-queue-entry-finished-request","at":8015,"chars":930},{"level":3,"title":"General dimensions","slug":"general-dimensions-3","at":8115,"chars":334},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-3","at":8449,"chars":496},{"level":2,"title":"Job queue entry finished (run)","slug":"job-queue-entry-finished-run","at":8945,"chars":704},{"level":3,"title":"General dimensions","slug":"general-dimensions-4","at":9027,"chars":507},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-4","at":9534,"chars":115},{"level":2,"title":"Job queue entry failed with error","slug":"job-queue-entry-failed-with-error","at":9649,"chars":2544},{"level":3,"title":"General dimensions","slug":"general-dimensions-5","at":9730,"chars":333},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-5","at":10063,"chars":115},{"level":3,"title":"Sample KQL code","slug":"sample-kql-code","at":10178,"chars":2015},{"level":2,"title":"Job queue entry {Job Queue Id} errored after {attempt number} attempts","slug":"job-queue-entry-job-queue-id-errored-after-attempt-number-attempts","at":12193,"chars":2921},{"level":3,"title":"General dimensions","slug":"general-dimensions-6","at":12364,"chars":364},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-6","at":12728,"chars":115},{"level":3,"title":"Sample KQL code","slug":"sample-kql-code-1","at":12843,"chars":2271},{"level":2,"title":"Job queue entry run by user","slug":"job-queue-entry-run-by-user","at":15114,"chars":644},{"level":3,"title":"General dimensions","slug":"general-dimensions-7","at":15326,"chars":317},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-7","at":15643,"chars":115},{"level":2,"title":"Job queue entry rescheduled on sign-in","slug":"job-queue-entry-rescheduled-on-sign-in","at":15758,"chars":765},{"level":3,"title":"General dimensions","slug":"general-dimensions-8","at":15921,"chars":352},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-8","at":16273,"chars":250},{"level":2,"title":"Job queue entry cancelled","slug":"job-queue-entry-cancelled","at":16523,"chars":725},{"level":3,"title":"General dimensions","slug":"general-dimensions-9","at":16682,"chars":346},{"level":3,"title":"Custom dimensions","slug":"custom-dimensions-9","at":17028,"chars":220},{"level":2,"title":"Job queues and performance","slug":"job-queues-and-performance","at":17248,"chars":605},{"level":2,"title":"Troubleshooting job queue issues with telemetry","slug":"troubleshooting-job-queue-issues-with-telemetry","at":17853,"chars":903},{"level":2,"title":"Alerting on job queue issues with telemetry","slug":"alerting-on-job-queue-issues-with-telemetry","at":18756,"chars":1611},{"level":2,"title":"Related information","slug":"related-information","at":20367,"chars":237}],"text":"# Analyzing job queue lifecycle telemetry\nAPPLIES TO: Business Central 2020 release wave 2, version 17.2, and later\nJob queue lifecycle telemetry gathers data about the following operations:\n A job queue entry was enqueued.\n A job queue entry was started.\n A job queue entry finished. Provides information as to whether it was successful or failed.\n A job queue entry was stopped.\n A job queue entry was cancelled.\n A job queue entry was scheduled on login.\n A job queue entry was run by a user.\nSee Use Job Queues to Schedule Tasks</admin-job-queues-schedule-tasks> in the Business Central application help.\nSee How the Job Queue works<../developer/devenv-job-queue> in the Business Central developer content.\nThe events below use `TelemetryScope::All`, except the successful run event AL000082C, which uses `TelemetryScope::ExtensionPublisher`.\n## Job queue telemetry events\nThe following table describes the event IDs that are currently emitted by the job queue system.\nEvent|Event id|Job queue status|Description\nJob queue entry enqueued|AL0000E24|Enqueued|Occurs when a job queue entry is enqueued to run at or after the specified alJobQueueEarliestStartDateTime.\nJob queue entry failed to be enqueued|AL0000FNY|Enqueued|Occurs when a job queue entry fails to enqueue and this happens if no task scheduler is created behind it.\nJob queue entry started|AL0000E25|Started|Occurs right before the `Job Queue Start codeunit` is triggered and that codeunit will run the specified `Object ID to run`.\nJob queue request finished|AL0000E26|Finished successfully|Occurs when a job queue request completes successfully.\nJob queue run finished|AL000082C|Finished successfully|Occurs when a job queue run completes successfully. This event is sent only to the extension publisher's telemetry resource.\nJob queue entry failed (might be retried)|AL0000HE7|Error|Occurs when a job queue errors, and this is the first thing that is triggered before the updating of records.\nJob queue entry rescheduled on sign-in|AL0000I49|N/A|Emitted when an eligible recurring job queue entry without a scheduled task is rescheduled after sign-in.\nJob queue entry run once by a user|AL0000FMG|N/A|Emitted after a user selects Run once (foreground) on the Job Queue Entries or Job Queue Entry Card page and confirms the action.\nJob queue entry failed for the last time and is set to stopped|AL0000JRG|Error|Emitted when the job queue entry fails for the very last time before being set in Error state.\nJob queue entry cancelled|AL0000KZV|N/A|Emitted when a job queue entry is cancelled. The event has normal severity (`1`).\n## Common custom dimensions to all job queue events\nThe following table explains custom dimensions that are common to all job queue entry telemetry events described below.\nDimension|Description or value\nalCategory|AL JobQueueEntries\naadTenantId|Specifies the Microsoft Entra tenant ID used for Microsoft Entra authentication. For on-premises, if you aren't using Microsoft Entra authentication, this value is common.\nenvironmentName|Specifies the name of the tenant environment. See Managing Environments<tenant-admin-center-environments>.\nenvironmentType|Specifies the environment type for the tenant, such as Production or Sandbox. See tenant-admin-center-environments#types-of-environments.\ncompanyName|The current company name.\nalJobQueueScheduledTaskId|Specifies the ID of the scheduled task.\nalJobQueueEarliestStartDateTime|Specifies the earliest start date/time for the job queue entry.\nalJobQueueId|Specifies the ID of the job queue entry.\nalJobQueueIsRecurring|Specifies whether the job queue is recurring. Yes indicates it's recurring. No indicates it's not recurring. These lifecycle events format values in the default application language.\nalJobQueueObjectId|Specifies the ID of the object that the job queue entry runs.\nalJobQueueObjectName|Specifies the name of the object that the job queue entry runs. </br></br>This dimension was introduced in version 22.0.\nalJobQueueObjectType|Specifies the type of the object that the job queue entry runs, for example Report or Codeunit.\nalJobQueueObjectDescription|Specifies the description of the object that the job queue entry runs. </br></br>This dimension was introduced in version 22.2.\nalJobQueueStacktrace|Specifies the AL error stack trace. It's included only in the error events AL0000HE7 and AL0000JRG. This dimension was introduced in version 21.3.\nalJobQueueCompanyName|Specifies the company that contains the job queue entry.\nalJobQueueMaxNumberOfAttemptsToRun|Specifies the maximum number of attempts configured for the entry. This dimension was introduced in version 21.5.\nalJobQueueNumberOfAttemptsToRun|Specifies the number of attempts to run the entry. This dimension was introduced in version 21.5.\nalJobQueueStatus|Ready indicates it's a non-recurring job queue entry or the first run of a recurring job queue entry that's ready to run. In Process indicates it's being run. Error indicates it encountered an error while running. On Hold indicates it's being queued. Finished indicates it's finished without error. On Hold with Inactivity Timeout indicates it's a recurring job query entry that's ready to run.\n## Job queue entry enqueued\nOccurs when a job queue entry is sent to the job queue to eventually be run. A job queue entry is sent to the queue when its status is changed from On Hold to Ready or if it's a recurring job queue entry. Recurring job queue entries are automatically enqueued after each run.\n### General dimensions\nDimension|Description or value\nmessage|Job queue entry enqueued: {alJobQueueId}\nseverityLevel|1\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\nThe following table explains custom dimensions that are specific to this trace.\nDimension|Description or value\neventId|AL0000E24\nalJobQueueId|Specifies the ID of the job queue entry.\nalJobQueueIsRecurring|Specifies whether the job queue is recurring. Yes indicates it's recurring. No indicates it's not recurring.\nalJobQueueObjectId|Specifies the ID of the object that the job queue entry runs.\nalJobQueueObjectType|Specifies the type of the object that the job queue entry runs, for example Report or Codeunit.\nalJobQueueObjectDescription|Specifies the description of the object that the job queue entry runs. This dimension was introduced in Business Central 2023 release wave 1, version 22.2.\nalJobQueueStatus|Ready indicates it's a non-recurring job queue entry or the first run of a recurring job queue entry that's ready to run. On Hold with Inactivity Timeout indicates it's a recurring job query entry that's ready to run.\n## Job queue entry failed to be enqueued\nInformation if the job queue entry fails to be sent to the queue.\n### General dimensions\nDimension|Description or value\nmessage|Job queue entry not enqueued: {alJobQueueId}\nseverityLevel|2\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\nThe following table explains custom dimensions that are specific to this trace.\n|Dimension|Description or value|\n|eventId|AL0000FNY|\n|See common custom dimensions<#other>||\n## Job queue entry started\nOccurs when a job queue entry starts to run.\n### General dimensions\nDimension|Description or value\nmessage|Job queue entry started: {alJobQueueId}\nseverityLevel|1\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\nThe following table explains custom dimensions that are specific to this trace.\n|Dimension|Description or value|\n|eventId|AL0000E25|\n|See common custom dimensions<#other>||\n## Job queue entry finished (request)\nOccurs when a request for a job queue entry finishes running.\n### General dimensions\nDimension|Description or value\nmessage|Job queue entry finished: {alJobQueueId}\nseverityLevel|1\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|AL0000E26|\n|alJobQueueExecutionTimeInMs|Specifies how many milliseconds it took to run the job queue entry.|\n|alJobQueueScheduledTaskId|Specifies the scheduled task ID for the request that finished, before any recurring entry was rescheduled.|\n|alJobQueueNextScheduledTaskId|Specifies the scheduled task ID stored on the entry after the request, such as the next task for a recurring entry.|\n|See common custom dimensions<#other>||\n## Job queue entry finished (run)\nOccurs when a job queue entry finishes running.\n### General dimensions\nDimension|Description or value\nmessage|JobID = {alJobQueueId}, ObjectType = {alJobQueueObjectType}, ObjectID = {alJobQueueObjectId}, Status = Finished, Result = Success, Company = {alJobQueueCompanyName}, Scheduled Task Id = {alJobQueueScheduledTaskId}\nseverityLevel|1\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|AL000082C|\n|See common custom dimensions<#other>||\n## Job queue entry failed with error\nOccurs when a job queue entry fails to run.\n### General dimensions\nDimension|Description or value\nmessage|Job queue entry errored: {alJobQueueId}\nseverityLevel|2\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|AL0000HE7|\n|See common custom dimensions<#other>||\n### Sample KQL code\nThis KQL code can help you get started troubleshooting job queue errors. Note that these failed entries might be restarted.\n```kql\n// Job queue entry run failed\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions.eventId == 'AL0000HE7'\n| project timestamp\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// Caller app dimensions identify the telemetry caller, not necessarily the app containing the job queue object.\n, jobQueueAppId = customDimensions.alCallerAppId\n, jobQueueAppName = customDimensions.alCallerAppName\n, jobQueueAppPublisher = customDimensions.alCallerPublisher\n, jobQueueAppVersion = customDimensions.alCallerAppVersion\n// jobQueueObject* dimensions contains the information about the object containing the code being run\n, jobQueueObjectId = customDimensions.alJobQueueObjectId\n, jobQueueObjectName = customDimensions.alJobQueueObjectName // added in 22.0\n, jobQueueObjectType = customDimensions.alJobQueueObjectType\n// jobQueueExecution dimensions contain information about the job queue entry definition\n, jobQueueEntryId = customDimensions.alJobQueueId\n, jobQueueEntryIsRecurring = customDimensions.alJobQueueIsRecurring\n, jobQueueEntryDescription = customDimensions.alJobQueueObjectDescription // added in 22.2\n, jobQueueEntryMaxNumberOfAttemptsToRun = customDimensions.alJobQueueMaxNumberOfAttemptsToRun // added in 21.5\n// jobQueueExecution dimensions contain information about the attempted run of the job queue entry\n, jobQueueExecutionNumberOfAttemptsToRun = customDimensions.alJobQueueNumberOfAttemptsToRun // added in 21.5\n, jobQueueExecutionStacktrace = customDimensions.alJobQueueStacktrace\n, jobQueueExecutionStatus = customDimensions.alJobQueueStatus\n, jobQueueExecutionTaskId = customDimensions.alJobQueueScheduledTaskId // you can join to task scheduler telemetry on the taskId\n```\n## Job queue entry {Job Queue Id} errored after {attempt number} attempts\nOccurs when a job queue entry fails to run. This telemetry event was introduced in version 21.5.\n### General dimensions\nDimension|Description or value\nmessage|Job queue entry {Job Queue Id} errored after {attempt number} attempts\nseverityLevel|2\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|AL0000JRG|\n|See common custom dimensions<#other>||\n### Sample KQL code\nThis KQL code can help you get started troubleshooting job queue errors where the entry has been stopped because it failed for the last time before being set to the Error state. As an administrator, you want to know about job queue entries that are going into the final failed state and require manual intervention, such as restarting.\n```kql\n// Job queue entry {Job Queue Id} errored after {attempt number} attempts\ntraces\n| where timestamp > ago(60d) // adjust as needed\n| where customDimensions.eventId == 'AL0000JRG'\n| project timestamp\n, aadTenantId = customDimensions.aadTenantId\n, environmentName = customDimensions.environmentName\n, environmentType = customDimensions.environmentType\n, companyName = customDimensions.companyName\n// Caller app dimensions identify the telemetry caller, not necessarily the app containing the job queue object.\n, jobQueueAppId = customDimensions.alCallerAppId\n, jobQueueAppName = customDimensions.alCallerAppName\n, jobQueueAppPublisher = customDimensions.alCallerPublisher\n, jobQueueAppVersion = customDimensions.alCallerAppVersion\n// jobQueueObject* dimensions contains the information about the object containing the code being run\n, jobQueueObjectId = customDimensions.alJobQueueObjectId\n, jobQueueObjectName = customDimensions.alJobQueueObjectName // added in 22.0\n, jobQueueObjectType = customDimensions.alJobQueueObjectType\n// jobQueueExecution dimensions contain information about the job queue entry definition\n, jobQueueEntryId = customDimensions.alJobQueueId\n, jobQueueEntryIsRecurring = customDimensions.alJobQueueIsRecurring\n, jobQueueEntryDescription = customDimensions.alJobQueueObjectDescription // added in 22.2\n, jobQueueEntryMaxNumberOfAttemptsToRun = customDimensions.alJobQueueMaxNumberOfAttemptsToRun // added in 21.5\n// jobQueueExecution dimensions contain information about the attempted run of the job queue entry\n, jobQueueExecutionNumberOfAttemptsToRun = customDimensions.alJobQueueNumberOfAttemptsToRun // added in 21.5\n, jobQueueExecutionStatus = customDimensions.alJobQueueStatus\n, jobQueueExecutionStacktrace = customDimensions.alJobQueueStacktrace\n, jobQueueExecutionTaskId = customDimensions.alJobQueueScheduledTaskId // you can join to task scheduler telemetry on the taskId\n```\n## Job queue entry run by user\nOccurs when a user selects Run once (foreground) on the Job Queue Entries or Job Queue Entry Card page and confirms the action. This telemetry event was introduced in version 22.2.\n### General dimensions\nDimension|Description or value\nmessage|Running job queue once.\nseverityLevel|1\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|AL0000FMG|\n|See common custom dimensions<#other>||\n## Job queue entry rescheduled on sign-in\nOccurs when a job queue entry was rescheduled when a user signs in. This telemetry event was introduced in version 22.0.\n### General dimensions\nDimension|Description or value\nmessage|Job queue entry rescheduled on login: {job queue entry id}\nseverityLevel|1\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|AL0000I49|\n|alJobQueueRescheduledNewTask|Specifies whether rescheduling created a new scheduled task rather than making the existing task ready.|\n|See common custom dimensions<#other>||\n## Job queue entry cancelled\nOccurs when cancellation of a job queue entry's scheduled task is attempted. This telemetry event was introduced in version 23.0.\n### General dimensions\nDimension|Description or value\nmessage|Job queue entry task cancelled: {job queue entry id}\nseverityLevel|1\nuser_Id|The user telemetry ID for the user. From the user card, you can use user_Id to identify the user who triggered this telemetry event. See telemetry-enable-application-insights#assign-a-telemetry-id-to-users.\n### Custom dimensions\n|Dimension|Description or value|\n|eventId|AL0000KZV|\n|alJobQueueScheduledTaskExistedOnCancel|Specifies whether cancellation of the scheduled task succeeded.|\n|See common custom dimensions<#other>||\n## Job queues and performance\nScheduled tasks or job queue entries that are set to run on a recurring schedule can impact the performance of Business Central under either of the following conditions:\n They run too frequently.\n  Consider how often the task or job needs to run. Especially for polling scenarios, you might have better and more performant ways to react, such as using webhooks.\n They run heavy jobs while many users are also using Business Central.\n  Consider running them outside working hours. This might decrease locking and deadlock issues both for users and for the task or job itself.\n## Troubleshooting job queue issues with telemetry\nThe reason for a failed job queue entry could be in the code that is running. You can find the owner (also called publisher) of the code in the AL stack trace dimension in the job queue error event AL0000HE7. If the error comes from an app/extension, you need to contact the owner of the code to get it resolved. If the error comes from the Microsoft application, then you need to open a support request with Microsoft to get it resolved.\nSee event AL0000HE7<#error>.\nIf a job queue entry fails after the maximum number of retry attempts has been done, the telemetry event AL0000JRG is emitted and the job queue entry is set to permanently being stopped. As an administrator, you want to know about these job queue entries that are going into the final failed state and require manual intervention (restarting etc).\nSee event AL0000JRG<#errorStopped>.\n## Alerting on job queue issues with telemetry\nIf something happens in your environment or app that you need to act on, you can set up a system that sends you an alert. Azure Application Insights makes it easy to define such alerts.\nYou can use the following tools to define and set up alerts on telemetry events:\n Azure Application Insights Alerts\n Azure Logic Apps\n Power Automate\nAll three approaches need a Kusto (KQL) query to define the alerting condition.\nThere are at least three job queue error scenarios where you might want to set up alerts:\n1. Some job queue entries fail\n2. Some job queue entries failed and have been stopped\n3. No job queue entries are running\nIn the table below, you can read more about the scenarios and get sample KQL code for the alerting conditions in your alerts.\nCondition|Area|Relevant for|Description|Event ID(s)|KQL sample code\nJob queue errors|Errors|VAR|Get alerted when job queue entries fail.|AL0000HE7|https://github.com/microsoft/BCTech/blob/master/samples/AppInsights/Alerts/AlertingKQLSamples/JobQueueFailures.kql\nJob queue stopped due to errors|Errors|VAR|Get alerted on job queue entries that are stopped due to recurring errors (because they have failed for all retry attempts).|AL0000JRG|https://github.com/microsoft/BCTech/blob/master/samples/AppInsights/Alerts/AlertingKQLSamples/JobQueueFailures.kql\nJob queue not running|Errors|VAR|Get alerted if no job queue entries have been started in a given time period.|AL0000E25|https://github.com/microsoft/BCTech/blob/master/samples/AppInsights/Alerts/AlertingKQLSamples/NoJobQueueRuns.kql\nSee telemetry-alert.\n## Related information\nUse Job Queues to Schedule Tasks</admin-job-queues-schedule-tasks>\nHow the Job Queue works<../developer/devenv-job-queue>\ntelemetry-overview\nEnabling Telemetry<telemetry-enable-application-insights>\ntelemetry-alert"}