Work with flow definitions

Publishing a flow definition
A flow definition must be published so that users can trigger a flow from it, and other flows can reference it. When a flow definition is unpublished, flows cannot be triggered, and other flows cannot reference it.
Holding a flow definition
You can hold a submitted flow definition. You do this when it has been scheduled to trigger automatically, but you do not want that automatic trigger to happen for some period of time. For example, you may do this when you first submit the flow definition but are not quite ready to put it into production, or when you require a maintenance window. The flow definition remains on hold until it the event triggers are explicitly enabled.
Releasing a flow definition from hold
When a flow definition is placed on hold, it cannot be triggered automatically until it has been explicitly released by enabling event triggers.
Deleting a flow definition
When you no longer require a flow definition, you can remove it from the list. If you delete a flow definition, and some flows belonging to the flow definition are still in the system, they are displayed in the job flow list under the adhoc Flow Definition Name.

Parent topic: Monitor and control your flow