Disabling accounts
You can stop a workflow or flow service from being executed.
About this task
Imagine you have the same account that is configured across multiple workflows or Flow services,
and you no longer want that account to be used. Instead of removing the account from each individual
workflow or Flow service, you can disable it from a central location. Disabling an account for an
application or external web service can be useful for several reasons, such as:
- A workflow or Flow service exceeds the request limit to an application or external web service, overwhelming the application or external web service.
- The application or external web service to which your workflow or Flow service sends requests faces server down issues.
- A workflow or Flow service is not critical, and you might want to temporarily halt its execution activity.
Disabling an account of an application or external web service is temporary. You can re-enable the account anytime based on your requirements.
Let’s now understand how to disable an account of an application or external web service and then enable the same account in detail.