Stop a running Flow

Overview

The user can manually request to stop the running flow.

It is not guaranteed that the flow will stop

When the end user stops the flow it is not guaranteed that the flow will be actually stopped. There are cases when the flow is stuck when executing not cancellable IO operation (for example, opening the  database connection with no configured timeout). In this case, the flow will continue running until it is finally able to stop or the Etlworks instance is rebooted.

Read about force execution.

Stop flow from the Flows screen

To stop a running Flow navigate the the Flows screen and click Stop flow button.

If multiple instances of the same flow are running at same time (for example when the flow is triggered by asynchronous HTTP listener) only the latest instance will be stopped. Read how to stop a specific instance of the running flow.

The Stop flow button is only available when the flow is in the Running state.

Stop flow from Flow Statistics dashboard

To stop a running Flow navigate the the Flows screen, select the status link which will open the Flow Statistics dashboard. Select the running (green) instance of the flow in the  History grid on a left and click the Stop flow button. 

If multiple instances of the same flow are running at same time (for example when the flow is triggered by asynchronous HTTP listener) you can stop each running instance individually. 

Flow status after user requested to stop it

Once the user requests to stop the flow, the status immediately changes from Running to Canceled. 

It will then change either to Error (when the regular flow is stopped) or Success (when the steaming flow is stopped).  At this point the flow is considered completely stopped.

Completely stopping a Flow may take up to a few minutes.