[BUG] "Include errors in response and allow workflows to continue" checkbox in API connector is broken

Mobile Beta
1

Hi forums,

In the mobile editor there’s a bug with the “allow workflows to continue” checkbox in the API connector. If an API returns an error, the workflow can’t continue even if this checkbox is checked. Furthermore, the “an Unhandled error has occured” event does not trigger if the API call returns an error either.

It seems impossible to figure out if an API call fails at the moment. If I enabled the new debug mode, the workflow hangs on the action making the API call and cannot proceed.

Here is the workflow:

image
image721×403 21.4 KB

And in the step by step debugger, we’re stuck here:

image
image911×549 42.2 KB

No amount of clicking next can do anything. I can think of some workarounds, but this seems like a pretty severe bug. In my case, I’m relying on the API response to decide if the user inputted a correct phone number.

In the console, I see this error when the debugger reaches the action:

image
image1920×1167 255 KB

All the best,

2

Unrelated, but this only triggers if the API call doesn’t have the allow workflows to continue checkbox (as if you allow it to continue, it’s a handled error)

1 Like
3

Makes sense, I was just trying to cover by bases and maybe find a temporary solution

4

Just tested, if I disable the checkbox and just try to use the Unhandled Error event, the workflow hangs and the event never fires. It seems that workflows that encounter an API error hang and can’t be re-run until I refresh the page :confused:

Edit: Also, all “click” workflows on the page become disabled until refresh :cry: completely bricks the app …

1 Like
5

Yeah there’s definitely still a bug in there.

6

Thanks for flagging @jonah.deleseleuc - have you filed a bug report for this yet?

1 Like
7

Yes I did, but it seems like someone fixed this today, or perhaps there’s a scenario that leads to this happening that I haven’t reproduced today yet.