Scenario run replay

{{scenario singular}} run replay is available on all plans {{scenario singular}} run replay is a capability that runs a current version of a scenario using trigger data from a previous {{scenario singular lowercase}} 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 multiple places in {{product name}} , depending on your goals /#builder test and debug new and existing {{scenario plural lowercase}} /#history and /#run details backfill data and recover 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 are successful /#builder in the {{scenario singular}} builder is ideal for testing, as it enables you to replay runs while building 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 /#builder to fix the error in the {{scenario singular}} builder, then /#history to replay the 99 errored runs from the {{scenario singular}} history or run details backfill data you can use replay to retroactively populate data in databases and 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}} /#history from the {{scenario singular}} history or run details is ideal for backfilling data, as this action doesn't require you to be in the {{scenario singular}} builder how it works when you replay a {{scenario singular lowercase}} run, a current version of a {{scenario singular lowercase}} runs using the trigger data of a previous run that data passes through all modules, even those that ran successfully the following data is stored for {{scenario singular lowercase}} run replays trigger output data docid 7odicud0ke9 tr4xwuiqn the most up to date 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}} history and consume credits if you see the note run cannot be replayed , this is likely because the following run types aren't stored check run a run scheduled by a docid\ bkdeyubelio6yvvcosrxj that did not return new data single module run a run of a single non docid\ bkdeyubelio6yvvcosrxj module where to find it you can replay {{scenario singular lowercase}} runs from the {{scenario singular}} builder, {{scenario singular}} history, and run details {{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 run in the {{scenario singular}} history 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 singular lowercase}} run, click the replay icon next to the details button optionally, click view run to view the replayed run in more detail in a new tab run details to find replay run in run details on the left sidebar, click scenarios select a {{scenario singular lowercase}} from the list in the {{scenario singular lowercase}} diagram, click a run in history click the replay run button to replay the run alternatively, click history , then the date or the details button click the replay run button to replay the run 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 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 alternatively, replay it from the run details after clicking the date or details this action injects the previous run's trigger data into the trigger module of the updated {{scenario singular lowercase}} the replayed run appears 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 https //www make com/en/pricing for details