Trace Jobs and Schedules in a GitHub Actions Workflow
Admin ·
The practice workflow runs a test job on a two-version Node.js matrix and makes the package job wait for the tests. Use it to check the dependency graph before you change a workflow.
Trace the package job back to the test job
Select Load example, then Validate GitHub Actions. The report shows two jobs, zero errors and zero warnings. The package job waits for test through needs. The runner job test has a matrix with Node.js 22 and 24.
Change needs: test to needs: checks under package. Validate again and find the error at /jobs/package/needs. Select Download github-actions-validation.json and inspect the matching missing-job code and source position.
Check the five cron fields
Reload the example. The schedule 20 6 * * MON-FRI specifies 06:20 on weekdays using the workflow's scheduled time zone, UTC when none is set. Change the first number from 20 to 70. The schedule-cron finding identifies the cron field because minutes run from 0 through 59.
Set the first number back to 20. If you add three or more jobs, keep the graph acyclic by tracing each job's needs back to earlier work.
GitHub Actions workflow syntaxGitHub Actions event and schedule reference
Check repository-specific settings on GitHub
The local check reads the YAML and recognized workflow fields. Review the availability of runner labels, referenced actions, secret values and reusable workflows in the repository that will run this file.
Common questions
Can I check a reusable workflow call?
Yes. The tool checks the reference's form and flags runner fields such as steps if they appear on a workflow-call job. The referenced workflow remains a separate file.
Why flag actions pinned to main?
The reference can point to a different commit as the branch moves. GitHub documents how to use an immutable commit SHA.