Scenario run replay

{{scenario singular}} run replay is available for users on all plans {{scenario singular}} run replay is a capability that allows you to run the last saved version of a scenario with trigger data from a previous scenario run this means you can test scenarios, resolve errors, and retroactively send data to third party systems without needing to obtain new data you can replay {{scenario singular lowercase}} runs in two places in make, depending on your goals scenario run replay /#builder testing and debugging new and existing {{scenario plural lowercase}} scenario run replay /#history backfilling data and recovering from errors in existing {{scenario plural lowercase}} why replay {{scenario singular lowercase}} runs many data events—such as payments, crm deals, or e commerce orders—are difficult to trigger on demand using trigger data from replayed {{scenario singular lowercase}} runs instead enables efficiency in each of the following use cases test and debug as you progressively build and test scenarios, the same data is processed multiple times instead of obtaining new data at each step, you can use trigger data from previous runs to ensure that new modules, routes, or fields work scenario run replay /#builder in the {{scenario singular}} builder is ideal for testing purposes, as it enables you to replay runs directly in the scenario builder without switching tabs recover from errors you can replay {{scenario singular lowercase}} runs to resolve logical errors, such as faulty filters, incorrect data mapping, or missing modules for example, if you have 100 errored runs due to a logical mistake, you can use scenario run replay /#builder to fix the error in the {{scenario singular}} builder, then /#history to replay the 99 errored runs in the {{scenario singular lowercase}} history backfill data you can use replay to backfill data—retroactively populate data in databases or third party systems—when errors in {{scenario plural lowercase}} result in corrupt or incomplete data, or when you forget to add data to a system after building a {{scenario singular lowercase}} docid\ ay1llxgjveo3e6shlof6o in the {{scenario singular lowercase}} history is ideal for backfilling data, as this simple action does not require you to work in the {{scenario singular}} builder how it works when you replay a {{scenario singular lowercase}} run, the last saved version of a {{scenario singular lowercase}} will run using the trigger data of a previous run that data passes through all modules, even those that ran successfully {{product name}} stores the following data for {{scenario singular lowercase}} run replays trigger output data scenario inputs and outputs docid 7odicud0ke9 tr4xwuiqn the most up to date variables docid\ dvn33b4od230cwt0cjpci value (values from previous runs are not preserved if updated during or since these runs) like standard {{scenario singular lowercase}} runs, replayed runs appear in the {{scenario singular lowercase}} history and consume credits where to find it you can replay {{scenario singular lowercase}} runs from the {{scenario singular}} builder and {{scenario singular lowercase}} history {{scenario singular}} builder to find run with existing data in the left sidebar, click scenarios select a {{scenario singular lowercase}} from your {{scenario plural lowercase}} list on the toolbar, click the down arrow next to the run once button select the {{scenario singular lowercase}} run to replay from the dropdown menu click the run once button {{scenario singular}} history to find replay scenario run on the left sidebar, click scenarios select a {{scenario singular lowercase}} from the list in the {{scenario singular lowercase}} diagram, click history to replay a scenario run, click the replay icon next to the details button examples in this example, you have a {{scenario singular lowercase}} that sends tally responses to a slack channel the example is for illustrative purposes only, and does not require you to build a scenario run with existing data your {{scenario singular lowercase}} watches responses in a tally form and sends them to a private slack channel as you build, you update the slack channel configured in the slack > create a message module in the {{scenario singular}} builder, you open the slack > create a message module settings, add the new slack channel, and save to test this change, you click the downward arrow next to the run once button on the toolbar in scenario run , you select a previous run to use for trigger data you click the run once button the change does not return errors, so you save the scenario for future use replay scenario run after a week of running your tally form {{scenario singular lowercase}} , you realize you should have also sent the responses to airtable you decide to replay the past week's run to backfill its data in airtable you update the scenario with an airtable module and click save alternatively, you can temporarily disable the route to slack to avoid sending the same responses again to backfill the past week's data into airtable, you replay last week's {{scenario singular lowercase}} run in history this action injects the previous run's trigger data into the trigger module of the updated {{scenario singular lowercase}} you can see the replayed run at the top of your {{scenario singular lowercase}} history the run resulted in 1 extra credit due to the added airtable module, totalling 3 credits your airtable database now includes data from the past week {{scenario singular}} run replay includes the following constraints bulk replay is currently not possible a {{scenario singular lowercase}} run is replayable as long as it's available in the {{scenario singular lowercase}} history, which varies by plan see log storage for details