Skip to content

Latest commit

 

History

History
48 lines (29 loc) · 2.18 KB

File metadata and controls

48 lines (29 loc) · 2.18 KB
title intro versions shortTitle
About troubleshooting workflows
You can use the tools in {% data variables.product.prodname_actions %} to debug your workflows.
fpt ghes ghec
*
*
*
About troubleshooting

{% data reusables.actions.enterprise-github-hosted-runners %}

Troubleshooting your workflows

There are several ways you can troubleshoot failed workflow runs.

{% ifversion copilot %}

Using {% data variables.product.prodname_copilot %}

If a workflow run fails, you can open a chat with {% data variables.product.prodname_copilot %} for assistance resolving the error. See AUTOTITLE.

{% endif %}

Using workflow run logs

Each workflow run generates activity logs that you can view, search, and download. For more information, see AUTOTITLE.

Enabling debug logging

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 AUTOTITLE.

Canceling a workflow

If you attempt to cancel a workflow and the cancellation doesn't succeed, make sure you aren't using the always expression. The always expression causes a workflow step to run even when the workflow is canceled, which results in a hanging cancellation. For more information, see AUTOTITLE.

{% ifversion actions-metrics %}

Troubleshooting {% data variables.product.prodname_actions %} inefficiencies

To analyze the inefficiencies and reliability of your workflows using metrics, see AUTOTITLE. {% endif %}

Troubleshooting self-hosted runners

If you use self-hosted runners, you can view their activity and diagnose common issues.

For more information, see AUTOTITLE.