Skip to content

Commit d5724bc

Browse files
author
Simonx Xu
authored
Merge pull request #9403 from MicrosoftDocs/main
Auto push to live 2025-07-23 10:01:55
2 parents 3a74297 + f5c223c commit d5724bc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

support/azure/automation/runbooks/job-not-start-as-expected.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot Issues with Runbook Execution Start Time
33
description: Discusses an issue where jobs don't start as expected in Azure Automation.
4-
ms.date: 06/27/2025
4+
ms.date: 07/23/2025
55
ms.reviewer: adoyle, v-weizhu
66
ms.service: azure-automation
77
ms.custom: sap:Runbook not working as expected
@@ -12,7 +12,7 @@ Process automation in Azure Automation allows you to create and manage PowerShel
1212

1313
## Service-level agreement (SLA)
1414

15-
The SLA for runbook automation is 30 minutes. It's expected that 99.999 percent of runbooks start within five minutes of the scheduled time. For more information, see [SLAs for Online Services](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services).
15+
The SLA for runbook automation is 30 minutes. It's expected that 99.9 percent of runbooks start within 30 minutes of the planned start time. For more information, see [SLAs for Online Services](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services).
1616

1717
The *SLA for the Automation Service - Process Automation* defines the following terms:
1818

0 commit comments

Comments
 (0)