Quick action to disable modules

We recently introduced a set of quality-of-life improvements to make daily work with our solution more seamless. One of these enhancements is the ability to disable a module directly by hovering over it, instead of opening its configuration and navigating to the general tab. This lets you quickly deactivate a module so it no longer processes messages—note that any subsequent modules will also stop receiving messages.

Disabling a module can be very useful when testing and debugging Flows. For example, when you want to find out why you get errors from a module, but don’t want the error to propagate to other modules. Or, when you want to validate the data produced by the Flow before sending it to external systems, by disabling the final output module.

Tip: These features are part of our regular release-notes.