Run after last item?

[Philip_Roberts]

I’m guessing this is likely a problem where an aggregator is the solution, but I think it could also be solved using sub scenerios but I haven’t been able to make it work right yet.

I have Scenario “A”

Module 3 output multiple bundles (zero, 2 or more)
The 1st bundle will route to the upper path, all others will route to the lower path.

What I want is to have another set of modules that run after the last bundle.

I’ve tried creating a second scenario that calls scenario A and having the “after last” processing there. Module 7 calls Scenario A.

However, I’ve found that when doing that, Scenario B continues execution immediately rather than waiting for Scenario A to run to completion.

Any suggestions? I’m happy to have this either all in 1 scenario or split across multiple.

[XenoMax]

You could change Scenario A to initiate from a Webhook module first. Then add the “Webhook Response” module at the end of the scenario, returning 200.

Then change Scenario B “Run a Scenario” to an HTTP module that sends a POST to the Webhook for Scenario A. It should wait for A to finish and return 200 before continuing.

[Philip_Roberts]

I’m not sure where I could put the WebHook Response in Scenario A to only get triggered once? In many cases, the lower line of modules will be run multiple times.

[XenoMax]

Add a 3rd route from the Router, and set the filter like this:

That way, once the final bundle from Stripe is running, and after the first 2 routes have checked/executed, the 3rd route will execute and you can stash the Webhook Response in there.

[Philip_Roberts]

That looks like it’s doing it.

I was misunderstanding the Router module + filters. Thought they were behaving more like a switch statement rather than sequential operations.

[XenoMax]

They behave as both, it’s down to how you configure your filters. Sometimes you don’t care about the order of the routes but here you actively exploit it