<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00007YosFXCAZOkta Identity EngineWorkflowsAnswered2025-01-31T09:00:17.000Z2022-04-07T06:29:20.000Z2022-04-12T17:30:09.000Z
  • flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery)

    Hi @1mwrl (1mwrl)​,

     

    Thank you for posting on our Okta community page to help you troubleshoot!

     

    I have done some research on my end and unfortunately, there is no option to cancel running executions in a flow and even if you turn off the flow, the executions already in motion will complete.

     

    I hope the above information is helpful!

    Expand Post
  • MaxKatz (Okta)

    Hi @1mwrl (1mwrl)​ - I'm curious, what is the use case where you need to stop a streaming action executing midway?

  • TimL.58332 (Workflows)

    One thing to keep in mind is any of the cards that send "down to a helper flow" require the helper flo be active. Turning the helper flo to an inactive state will cause the next "new" object passed to return "Flo is not active"

     

    Streaming inherently uses a high & non-modifiable concurrency. So any of the objects already in the pipeline (which can be a lot) will need to run to completion before the "flo is not active" error kicks off effectively killing the flo.

     

    So while it is technically accurate that you cannot kill an execution that is already in the pipeline when you are doing some sort of iteration to a helper flow you can stop the helper flow preventing new executions from reaching the pipeline effectively killing the flo.

    Expand Post
This question is closed.
Loading
Okta Workflow