I used to be able to click Run on my scenario to run it manually and test whatever I needed to test while having disconnected parts of my scenario that I’m not currently using, either from old iterations or ongoing development. Lately if I try to run a scenario manually and I have any disconnected components that are no longer valid because I’ve changed something, it gives me a warning, which is erroneous because I don’t need to pay attention to it at all. There are boxes to check that say “Ignore warning” but there’s no Save or Continue button. If I save the scenario after checking those boxes, nothing happens and again I can not run the scenario manually. It stops it entirely unless I delete or update all of the unused scenario bubbles. I don’t know why this bug was introduced but it’s killing me because it stops me from building anything out without starting fresh each time.
What is the problem & what have you tried?
Can’t run scenario manually when there are disconnected components that are no longer being used and don’t match up to some part of the scenario.
Error messages or input/output bundles
Filter before ‘Email - Send an Email’ [module ID 95] references inaccessible module ‘Webhooks - Custom webhook’ [module ID 41].
I have been experiencing this too, and its quite annoying.
Shouldnt have to leave everything connected, or add extra router modules, disable the routes to set things up. All a load of extra clicks that arent needed.
Need something better in the world of Claude Code, and MCPs.
the error shows that a filter in the active part of the scenario is referencing a disconnected module. So either delete the filter or change it to not do that.
This is usually not a manual-run bug. One of your disconnected routes still has a filter or mapping that references a deleted/inaccessible module, so Make blocks the run during validation. In your case, the filter before Send an Email still references Custom webhook [41]. Open that disconnected path and remove/update the broken filter/mappings, or delete that unused route entirely. Once those invalid references are gone, manual run should work again.
I’m sorry no, this is not how it has been, and this way makes quite difficult and time consuming to build and manage scenarios.
As a builder, often we often need to disconnect branches, disable filters when testing a specific part of the workflow or automation.
To say that testing one route requires me to delete and remove 20 other filters and module variables to test a route is not good at all.
Before, as long as the path was disconnected, Make would only check the modules, and filters are in place for the active, enables and connected routes.
And to be honest I have seen instances where the scenario will run even with missing or invalid variables in the modules.
This has always been the case - if you mapped something from a module and then deleted the module or disconnected it, the scenario will not run. It never did.
And yes, testing something requires valid data. It always did.
You cant run a flow where it expects something from module 20 and there is no module 20 in it. In no version of Integromat or Make could you do that.
What was the case before, was as long as the module or filter with invalid variables was disconnected from the live path, one could run the scenario fully.
Currently, it needs all invalid variables removed complete from the scenario before it can be run.
So should I want to run a test, and reconnect a removed branch, I need to now add-in all the modules and variables, which is unnecessary.
Image below shows an active running scenario, that has invalid variables in it. If I wanted to run, or switch the scenario on, I would have to remove all the invalid variables and modules. Not good.
The scenario is as pictured. The disconnected module is disconnected, and not is not on a main path. Not sure where you are seeing main path from
The filter with the errror references a module that is not connected to the main path at all, and yet it runs, and the scenario is saved, as it was before.
Hi @Kofi I agree, this worked before and is more difficult now. I also often have test disconnected sections & it’s very handy to run the scenario without having to now edit these.
Reported this a week ago. Just got the supports response that it has been fixed. not sure how other test their scenario, but most of us simply disconnect the parts we do not want to run. makes testing quick and easy. happy to see it got fixed quickly.
What is your goal?
What is the problem & what have you tried?
Error messages or input/output bundles