Some parts of scenario still run and throws errors even when filter stops scenario run after first module/trigger

[csana]

What is your goal?

To run a scenario.

What is the problem & what have you tried?

Hi, I have a scenario with a filter and two conditions after the trigger module.

Problem is some parts of the scenario still runs with empty data when nothing passes the filter.

This just consumes operations and throws multiple errors.

Please advise.

[Henk-Operative]

Hi @csana,

Please share more information about your scenario and the exact error you receive. You can share your scenario with the new share functionality in the editor:

Or share some screenshots/recordings.

Thanks!

Cheers,
Henk

[csana]

Hi, I can’t share as it contains some sensitive info. But here are screenshots:

[samliew]

That is because you are using aggregators that combines values from the trigger module.

Aggregators always run to completion as they “close” the “loop”. To avoid this, do not aggregate unnecessarily from the trigger module (as the “Source Module”).

Alternatively, you can prevent the rest of the scenario from running if there are nothing to aggregate. This option can be found in the aggregator’s “Advanced settings”.

You can also learn more about this in these Make Academy units:

An introduction to aggregators

• Introducing Aggregators
• Numeric Aggregators in action
• Text Aggregators in action

Introduction to Iterators and Array aggregators

• Importing JSON into a new scenario
• Iterating an array into bundles
• Aggregating an array from bundles
• Iterator and Aggregator use cases

Hope this helps! If you are still having trouble, please provide more details.

— @samliew