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.)
Select an option, then click Submit answer.
Reference / correct answer:
A workflow sends requests to a service that is down.
Most accepted answer: D. A workflow sends requests to a service that is down.
Community votes: B=2, D=3
Selected Answer: BD B. If a workflow is misbehaving and causing problems (e.g., spamming an API), temporarily disabling it prevents further damage without deleting the workflow file. D. If the target service is unavailable, running the workflow could produce errors or unnecessary failures. Disabling it temporarily prevents failed runs until the service is restored. upvoted 1 times
Selected Answer: BD 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. Key Point in Question → Answer Connection: The word "temporarily" is crucial - it indicates short-term external problems (service down, buggy code) rather than permanent configuration changes or normal operational needs. Disabling preserves workflow history and configuration. Use it for temporary issues you expect to resolve, not for permanent changes. upvoted 1 times
Selected Answer: D I’m going with D because the others are clearly non-starters. upvoted 1 times