Router fallback filter reappears after save (bundle does not pass filter)

Questions
1

:bullseye: What is your goal?

Route the scenario based on whether Google Sheets “Search Rows” finds an existing record:

– Continue down one path when a row is found

– Continue down another path when no row is found

:thinking: What is the problem & what have you tried?

Hi everyone,

I’m running into an issue with a Router after a Google Sheets “Search Rows” module.

Setup (simplified):
Webhook → Google Sheets (Search Rows) → Router

Goal:
• Route A when a row is found
• Route B when no row is found (fallback)

What I’ve done:
• Route A filter: Total number of bundles > 0
• Route B set as fallback
• No condition on fallback route

Issue:
After saving the fallback route, a blank condition reappears automatically (Text operators / Equal to).
When the scenario runs, it stops at Flow Control with:
“Bundle did not pass through the filter”

Even when the fallback condition is deleted and saved correctly, it reappears on the next edit/run.

Question:
Is this a known Router fallback behaviour or UI bug?
Is the recommended approach to avoid fallback entirely and use explicit numeric filters instead?

Thanks in advance.

:clipboard: Error messages or input/output bundles

Google Sheets “Search Rows” returns:
– Total number of bundles = 0 (new user case)

or

– Total number of bundles = 1 (existing user case)

Router stops execution with “bundle did not pass through the filter”
even though routes are configured for:

– bundles > 0

– bundles = 0 / fallback

1 Like
3

Hi @Johnny_Masson ,

Could you please share the blueprint of the scenario so we can troubleshoot the issue more effectively?

Reviewing the complete blueprint will help us analyze the setup in detail and identify the root cause.

Best regards,
Msquare Automation
Platinum Partner of Make
@Msquare_Automation