<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
0D54z00007MmlDUCAZOkta Identity EngineWorkflowsAnswered2024-04-03T16:09:08.000Z2022-01-04T22:02:22.000Z2022-02-07T20:27:04.000Z

MatthewH.10249 (State of Iowa) asked a question.

Why are "Call Flow Async" cards not allowed in "If Error" card?

Why are "Call Flow Async" cards not allowed in "If Error" card? In the "Try" area of the "If Error" card first contains an Okta API "Read User" card and is the card I'm interested in know if it fails or not. If it does not fail I want to make an async child flow call and continue on but if the Okta API "Read User" card fails I want the "Error" area to record the error and continue on without calling the async child flow. When I try to save the Workflow this way I don't get an error but the "save" button blanks out and it does not save. If I refresh the page it say there are unsubmitted changes.

 

Is there a reason "Call Flow Async" cards cannot be placed inside of an "If Error" card or is this a bug? As a work around I pulled the "Call Flow Async" card out of the "If Error" and placed it in an "If/Else" card immediately aft


  • @MatthewH.10249 (State of Iowa)​ 

     

    Sorry for seeing this late. I can't seem to repro, so I'm assuming the issue has been resolved.

     

    call async card inside of an if error 

    One guess as to why it might've been unhappy could be that the Call Flow Async card just fires off regardless and doesn't return any indication of success or failure to the caller flow, but you should still be able to add the card in the block to satisfy your use-case.

    Expand Post
    Selected as Best
This question is closed.
Loading
Why are "Call Flow Async" cards not allowed in "If Error" card?