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? (Choose two.)
A.
A workflow sends requests to a service that is down.
B.
A workflow error produces too many, or wrong, requests, impacting external services negatively.
C.
A workflow is configured to run on self-hosted runners
D.
A workflow needs to be changed from running on a schedule to a manual trigger
E.
A runner needs to have diagnostic logging enabled.
If a workflow depends on an external service that is down, disabling the workflow temporarily will prevent it from running and sending requests to the service, thus avoiding failed requests or unnecessary retries.
If a workflow is causing a negative impact on external services by generating too many requests or incorrect data due to a bug, temporarily disabling the workflow will stop this behavior while the issue is fixed.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit