To identify any constraints with concurrency or queuing, you can check how many jobs are currently being processed on the GitHub-hosted runners in your organization or enterprise.
For more information, see "Monitoring your current jobs."
Every workflow run generates a real-time graph that illustrates the run progress. You can use this graph to monitor and debug workflows. For example:
For more information, see "Using the visualization graph."
A status badge shows whether a workflow is currently failing or passing. A common place to add a status badge is in the
README.md file of your repository, but you can add it to any web page you'd like. By default, badges display the status of your default branch. You can also display the status of a workflow run for a specific branch or event using the
event query parameters in the URL.
For more information, see "Adding a workflow status badge."
To identify how long a job took to run, you can view its execution time. For example:
For more information, see "Viewing job execution time."
You can view the status of each job and step in a workflow. For example:
For more information, see "Viewing workflow run history."
Each workflow run generates activity logs that you can view, search, and download. For example:
For more information, see "Using workflow run logs."
If the workflow logs do not provide enough detail to diagnose why a workflow, job, or step is not working as expected, you can enable additional debug logging. For more information, see "Enabling debug logging."
If you use self-hosted runners, you can view their activity and diagnose common issues.
For more information, see "Monitoring and troubleshooting self-hosted runners."