Scenario run replay and naming capabilities now available
Both scenario run replay and customize run name are available on all plans.
You can now replay scenario runs to easily test scenarios and backfill data, and customize scenario run names to distinguish between runs in the scenario history.
Scenario run replay
Scenario run replay uses trigger data from a previous run in a current version of the scenario. This allows you to test scenarios, resolve errors, and backfill data without obtaining new trigger data.
You can use scenario run replay in two locations in Make, depending on your use case:
- Scenario Builder: Use Run with existing data (in the Run once dropdown) for easy testing and debugging as you build scenarios. This capability replays a previous run's trigger data on the current version of the scenario you're working on, even if unsaved.

- Scenario history: Use Replay scenario run (next to the Details button) to backfill data or replay errored runs after resolving errors. This capability replays a previous run's trigger data on the last-saved version of your scenario.

Replayed runs appear in your scenario history and consume creditsconsume credits like standard runs.
Customize run name
You can now define custom names for scenario runs using the Scenarios > Customize run name module. This helps you identify and search for specific runs in your scenario historyscenario history.
Add this module anywhere in your scenario route to name runs conditionally based on data mapped from a preceding module. Custom run names appear in the Run name column of the scenario history.
To find Customize run name, create a new scenario, or click on a scenario in your scenarios list. In the Scenario Builder, add the Scenarios > Customize run name module to a scenario.

As the Customize run name module does not use any credits, you can add clarity to your scenario runs for free.
Learn more
To find out more about scenario run replay and naming in Make, head to our Help Center: