Scenario run replay

scenario run replay is available for users on all plans scenario run replay allows you to use trigger data from an earlier run as mock data in your last saved {{scenario singular lowercase}} this feature helps you efficiently test your {{scenario plural lowercase}} and reduces the time spent manually adding data to find scenario run replay, select a {{scenario singular lowercase}} from your {{scenario plural lowercase}} list and click history the replay icon next to the details button replays a previous run when to use scenario run replay testing {{scenario plural lowercase}} often requires reprocessing the same data until errors are resolved however, many data events—such as payments, deals in crm systems, or e commerce orders—are difficult to retrieve on demand in these cases, manually re triggering data for reprocessing can be time consuming and frustrating scenario run replays can help address this issue, especially when you need to add modules to an existing {{scenario plural lowercase}} correct logical errors such as faulty filters, incorrect data mapping, or missing modules repopulate data in third party systems after errors in {{scenario plural lowercase}} resulted in corrupt or incomplete data how scenario run replay works when you replay a scenario run, the last saved version of a {{scenario singular lowercase}} runs again using trigger data from an earlier run that data passes through all modules, even those that ran successfully in the previous run {{product name}} stores the following data for scenario run replays trigger output data scenario inputs and outputs docid 7odicud0ke9 tr4xwuiqn the most up to date variables docid\ dvn33b4od230cwt0cjpci value (values from previous scenario runs are not preserved if updated during or since these runs) after a scenario run replay, you can see the replayed run at the top of the {{scenario singular lowercase}} history, i ncluding its credits use d and a link to the original run run replays consume credits docid\ hh nrtakeqakbmg63uuin in the same way as {{scenario singular lowercase}} runs scenario run replays include the following constraints bulk replay is currently not possible a scenario run is replayable as long as it's available in the {{scenario singular lowercase}} history, which varies by plan (see log storage ) example the following example of scenario run replay is for illustrative purposes only, and you will not need to build a scenario in this example, you built a {{scenario singular lowercase}} that sends tally form responses to a slack channel after a week of running the scenario, you realize you should have also sent the responses to airtable you decide to replay that week's run to backfill its data in airtable your original {{scenario singular lowercase}} watches responses in a tally form and sends all responses to a slack channel 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 run in history this action injects the previous run's trigger data into the trigger, tally > watch new responses , of the updated {{scenario singular lowercase}} you can see the replayed run at the top of your {{scenario singular lowercase}} history it resulted in 1 extra credit due to the added airtable module, totalling 3 credits your airtable database now includes data from the previous week