GH-200 · Question #58
Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. In which scenarios would temporarily disabling a workflow be most useful?…
The correct answer is B. A workflow error produces too many, or wrong, requests, impacting external services negatively. D. A workflow sends requests to a service that is down. Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful: [B] A workflow error that produces too many or wrong requests, impacting external services A workflow that is not critical and is consuming…
Question
Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. In which scenarios would temporarily disabling a workflow be most useful? (Each correct answer presents a complete solution. Choose two.)
Options
- AA runner needs to have diagnostic logging enabled.
- BA workflow error produces too many, or wrong, requests, impacting external services negatively.
- CA workflow is configured to run on self-hosted runners.
- DA workflow sends requests to a service that is down.
- EA workflow needs to be changed from running on a schedule to a manual trigger.
How the community answered
(29 responses)- A3% (1)
- B76% (22)
- C14% (4)
- E7% (2)
Explanation
Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful: [B] A workflow error that produces too many or wrong requests, impacting external services A workflow that is not critical and is consuming too many minutes on your account. [D] A workflow that sends requests to a service that is down. Workflows on a forked repository that aren't needed (for example, scheduled workflows). https://docs.github.com/en/actions/how-tos/manage-workflow-runs/disable-and-enable-workflows
Topics
Community Discussion
No community discussion yet for this question.