Merge pull request #210055 from SnehaSudhirG/02Sept-JobCreation

edited the troubleshooting scenario

Author: prmerger-automator[bot]

articles/automation/troubleshoot/runbooks.md

@@ -47,19 +47,15 @@ When you receive errors during runbook execution in Azure Automation, you can us
 ## Scenario: Unable to create new Automation job in West Europe region
 
 ### Issue
-When creating new Automation jobs, you might experience a delay or failure of job creation.
+When creating new Automation jobs, you might experience a delay or failure of job creation. Scheduled jobs will automatically be retired, and jobs executed through the portal can be retired if you see a failure. 
 
 ### Cause
-This is because of scalability limits with the Automation service in the West Europe region.
+This is because of the high load from customers' runbooks using the Automation service in the West Europe region.
 
 ### Resolution
-Do one of the following actions if it is feasible as per your requirement and environment to reduce the chance of failure: 
+Perform the following action if it is feasible as per your requirement and environment to reduce the chance of failure: 
 
-- During the peak hours of job creation, typically on the hour, and half hour, move the job start time to five minutes before or after the hour/half hour.
-- Run the Automation jobs from alternate data centres until the transition work is complete.
-
->[!NOTE]
-> The optimization of existing load and transitioning the load to a new design by the product group is in progress.
+- If you’re using the top of the hour for the job creation (at 12:00, 1:00, 2:00, and so on.), typically on the hour, or half hour, we recommend that you move the job start time to five minutes before or after the hour/half hour. This is because a most of the customers use the beginning of the hour for job execution which drastically increases the load on the service, while the load is relatively low at the other time slots.
 
 ## <a name="runbook-fails-no-permission"></a>Scenario: Runbook fails with "this.Client.SubscriptionId cannot be null." error message