The module run panel changed how I debug client scenarios

Make recently added a new Module run panel in the Scenario Builder, and after a couple of weeks using it I wanted to share how it changed my debugging routine.

Where to find it: run your scenario once (or run a single module), then click the output bubble above the module in the editor (the small ✓ bubble that appears after a run). That opens the run panel for that module. I have attached a screenshot of it below.

What it shows: the input and output of each operation for that module, side by side, with a Fields/JSON toggle at the top and an operation picker, so you can flip through past operations without opening the full execution history. You can also run the module again using data from an earlier operation, which is handy when you need to re-test with the exact bundle that caused a failure.

Where it actually saves me time:

  1. Long scenarios with 30 plus modules. Before, testing one branch meant running everything upstream of it, which could trigger real side effects on live data. Now I run just the module I am changing with a sample bundle and leave the rest alone.

  2. Modules that fail only on certain data. Instead of replaying the whole scenario until the bad record shows up, I pick the past operation that had the bad bundle and rerun just this module with it. A failure in isolation is much easier to read.

  3. Onboarding on an inherited scenario. Running modules one at a time down the chain is a quick way to learn what each one does before I touch anything.

One caution: a module run in isolation still does the real thing. If the module creates records or sends emails, point it at test data first. I keep sandbox copies of client setups for exactly this.

Small feature, but it cut a real chunk off my debugging time, especially on the wide scenarios people hand over after someone else built them.

Thanks for writing this up. Rerunning a module with an old operation is my favorite part too.

Two small things I would add from my side:

When a client reports a bad record, I switch to the JSON view and save that exact bundle in a note next to the ticket. After I fix the scenario, I rerun the module with the same bundle, so I know the fix really covers the case that broke.

For HTTP modules, I always look at the output body in the JSON view, not only the status code. Some APIs return 200 with an error message inside the body, so the scenario looks green even though nothing was created. Having the raw body right there in the panel makes that much easier to spot.

And fully agree on the sandbox point. It is easy to forget that running a single module still does the real thing.