Fallback Option on a Router triggers, even though the other route triggered first

Hey Guys,

am I missing something? I tried to use this setup to check Microsoft 365 People for new users and updated info. If The user already exists (in the Excel list), their Info is updated. this is the first path. The second path which should be the fallback option creates a new row in the Excel table. But now both paths activate if the first path activates. Where is my mistake?


blueprint.json (94.8 KB)

Hi @Benedict_Manousidis,

I just tested how callback works :
callbackfeature.json (11.8 KB)

This also behaves the same way even if you include a filter before Add a Row as you did (length = position) :

Now thinking about the ‘List Table Rows’ module - it should generate multiple bundles. Are you sure it’s the same Bundle that goes into both filters? I doubt it.

Hi @kudrachaa,

first of all, thank you for taking thetime to answer.
List table rows generates a whole bunch of bundles. It is not the same bundle numerically but the same person who is first selected via the test run.
I initially thought the fallback option only triggers if no other path gets past their filter. Do I need to add an additional filter to prevent my fallback route from triggering? If so how do I do that?

Thanks a lot

I see. Here in google sheets we’d use Search rows function and not List Rows, but in Excel I can’t see that.

What you’re doing here is searching for name1 in : [name5,name6,name1] and this will output [name5,name1,name6,name1,name1*] name1* = updated name1. It essentially runs the program for EACH LINE.

One of the methods to run this program would be :

==> Artificially throw an Error (my method is parse JSON with {emptystring} value) and then add error handling with Commit

What this will do is go through filter 1 and search for the name, and if the filter goes through, execute the script and then throw an error in the end of branch 1. This will terminate the scenario and even if in filter 2 bundle position=bundle total in the second filter, it won’t be executed. But if the name isn’t found : the error will not be thrown in branch 1 and filter 2 can be successfully executed - so the row will be added.

Note : this solution is only applicable if Watch Contacts Limit is set to 1. Else the error will ignore any other contacts than the first one.

Hope it helps.