Guide users to schedule workflows at lower load times (#18362)

Author: Sarah Edwards

content/actions/guides/scheduling-issue-creation.md

@@ -34,7 +34,7 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
     name: Weekly Team Sync
     on:
       schedule:
-        - cron: 0 07 * * 1
+        - cron: 20 07 * * 1
 
     jobs:
       create_issue:
@@ -66,7 +66,7 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
     ```
     {% endraw %}
 4. Customize the parameters in your workflow file:
-   - Change the value for `on.schedule` to dictate when you want this workflow to run. In the example above, the workflow will run every Monday at 7:00 UTC. For more information about scheduled workflows, see "[Scheduled events](/actions/reference/events-that-trigger-workflows#scheduled-events)."
+   - Change the value for `on.schedule` to dictate when you want this workflow to run. In the example above, the workflow will run every Monday at 7:20 UTC. For more information about scheduled workflows, see "[Scheduled events](/actions/reference/events-that-trigger-workflows#scheduled-events)."
    - Change the value for `assignees` to the list of {% data variables.product.prodname_dotcom %} usernames that you want to assign to the issue.
    - Change the value for `labels` to the list of labels that you want to apply to the issue.
    - Change the value for `title` to the title that you want the issue to have.
@@ -77,7 +77,7 @@ In the tutorial, you will first make a workflow file that uses the [`imjohnbo/is
 
 ### Expected results
 
-Based on the `schedule` parameter (for example, every Monday at 7:00 UTC), your workflow will create a new issue with the assignees, labels, title, and body that you specified. If you set `pinned` to `true`, the workflow will pin the issue to your repository. If you set `close-previous` to true, the workflow will close the most recent issue with matching labels.
+Based on the `schedule` parameter (for example, every Monday at 7:20 UTC), your workflow will create a new issue with the assignees, labels, title, and body that you specified. If you set `pinned` to `true`, the workflow will pin the issue to your repository. If you set `close-previous` to true, the workflow will close the most recent issue with matching labels.
 
 {% data reusables.actions.schedule-delay %}
 

content/code-security/secure-coding/configuring-code-scanning.md

@@ -104,13 +104,13 @@ on:
   pull_request:
     branches: [main]
   schedule:
-    - cron: '0 15 * * 0'
+    - cron: '20 14 * * 1'
 ```
 
 This workflow scans:
 * Every push to the default branch and the protected branch
 * Every pull request to the default branch
-* The default branch at 3 P.M. every Sunday
+* The default branch every Monday at 14:20 UTC
 
 ### Specifying an operating system
 

content/code-security/secure-coding/running-codeql-code-scanning-in-a-container.md

@@ -42,7 +42,7 @@ on:
   pull_request:
     branches: [main]
   schedule:
-    - cron: '0 0 * * 0'
+    - cron: '15 5 * * 3'
 
 jobs:
   analyze:

content/code-security/secure-coding/uploading-a-sarif-file-to-github.md

@@ -59,11 +59,11 @@ Alternatively, you could modify this workflow to upload a directory of SARIF fil
 name: "Upload SARIF"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
-# The scheduled workflow runs every at 00:00 on Sunday UTC time.
+# The scheduled workflow runs every Thursday at 15:45 UTC.
 on:
   push:
   schedule:
-  - cron: '0 0 * * 0'
+  - cron: '45 15 * * 4'
 
 jobs:
   build:
@@ -91,11 +91,11 @@ The workflow shows an example of running the ESLint static analysis tool as a st
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
-# The scheduled workflow runs every at 00:00 on Sunday UTC time.
+# The scheduled workflow runs every Wednesday at 15:45 UTC.
 on:
   push:
   schedule:
-  - cron: '0 0 * * 0'
+  - cron: '45 15 * * 3'
 
 jobs:
   build:

content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning.md

@@ -100,13 +100,13 @@ on:
   pull_request:
     branches: [main]
   schedule:
-    - cron: '0 15 * * 0'
+    - cron: '40 7 * * 2'
 ```
 
 This workflow scans:
 * Every push to the default branch and the protected branch
 * Every pull request to the default branch
-* The default branch at 3 P.M. every Sunday
+* The default branch every Tuesday at 7:40 UTC
 
 ### Specifying an operating system
 

content/github/finding-security-vulnerabilities-and-errors-in-your-code/running-codeql-code-scanning-in-a-container.md

@@ -38,7 +38,7 @@ on:
   pull_request:
     branches: [main]
   schedule:
-    - cron: '0 0 * * 0'
+    - cron: '45 15 * * 2'
 
 jobs:
   analyze:

content/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github.md

@@ -54,11 +54,11 @@ Alternatively, you could modify this workflow to upload a directory of SARIF fil
 name: "Upload SARIF"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
-# The scheduled workflow runs every at 00:00 on Sunday UTC time.
+# The scheduled workflow runs every Friday at 15:45 UTC.
 on:
   push:
   schedule:
-  - cron: '0 0 * * 0'
+  - cron: '45 15 * * 5'
 
 jobs:
   build:
@@ -86,11 +86,11 @@ The workflow shows an example of running the ESLint static analysis tool as a st
 name: "ESLint analysis"
 
 # Run workflow each time code is pushed to your repository and on a schedule.
-# The scheduled workflow runs every at 00:00 on Sunday UTC time.
+# The scheduled workflow runs every Monday at 15:45 UTC.
 on:
   push:
   schedule:
-  - cron: '0 0 * * 0'
+  - cron: '45 15 * * 1'
 
 jobs:
   build:

data/reusables/actions/schedule-delay.md

@@ -1,5 +1,5 @@
 {% note %}
 
-Note: The `schedule` event can be delayed during periods of high loads of {% data variables.product.prodname_actions %} workflow runs.
+Note: The `schedule` event can be delayed during periods of high loads of {% data variables.product.prodname_actions %} workflow runs. High load times include the start of every hour. To decrease the chance of delay, schedule your workflow to run at a different time of the hour.
 
 {% endnote %}

data/reusables/repositories/actions-scheduled-workflow-example.md

@@ -1,11 +1,11 @@
 You can schedule a workflow to run at specific UTC times using [POSIX cron syntax](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/crontab.html#tag_20_25_07). Scheduled workflows run on the latest commit on the default or base branch. The shortest interval you can run scheduled workflows is once every 5 minutes.
 
-This example triggers the workflow every 15 minutes:
+This example triggers the workflow every day at 5:30 and 17:30 UTC:
 
 ```yaml
 on:
   schedule:
     # * is a special character in YAML so you have to quote this string
-    - cron:  '*/15 * * * *'
+    - cron:  '*/30 5,17 * * *'
 
 ```