--- title: Scenario history slug: scenario-history description: Monitor execution history and user changes, and export logs for debugging and analysis image: https://archbee-image-uploads.s3.amazonaws.com/oAyFj2GHlBeBVWF5OAir2/EIvMMFhz9kRkY2jp6Ni4I_4.png docTags: createdAt: 2025-02-03T13:29:15.599Z --- ****Scenario history contains information about scenario runs and user changes to the scenario. To find it, click a scenario in the scenario list, then go to the **History **tab. ::embed[]{url="https://www.youtube.com/watch?v=ZSI0mxFXv8Y"} ## Scenario run and change log entries In the Scenario history, scenario run entries include the following information: - Run date and time - [Run name](https://apps.make.com/scenario-service#customize-run-name) - Trigger or activity type - Status (Success, Warning, Error) - Run duration - [Operations](docId\:ZR2rWmILMJ_19R85MlAwM) completed - [Credits](docId\:hh-nrTakEqakBmg63UUiN) consumed - Size of transferred data - Source run - [Scenario run replay](docId\:ay1LLXGjveo3e6ShLOf6O) - [Details](./#history-details) Change log entries record the following user actions: - Scenario scheduling changes - Scenario edits - Scenario activation :::hint{type="success"} The number of days your scenario run history entries are stored depends on your pricing plan. For details, see Make's [pricing page](https://www.make.com/en/pricing). ::: ## Scenario history details You can view full information about a specific scenario run, including the bundles processed, in the **Details** of the **History** tab. This allows you to inspect module outputs and logs and understand how a scenario behaved – for example, if a module returned an unexpected value. To view scenario run details: ::::WorkflowBlock :::WorkflowBlockItem Find the scenario run entry in the **History** tab. ::: :::WorkflowBlockItem Click **Details** on the right-hand side of the entry. ::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/BqDowlWKLNs3qkVpO_VXY-20260312-164321.png" size="70" width="2518" height="1018" position="center" darkWidth="2518" darkHeight="1018" showCaption="false"} ::: :::: In **Details**, you can: 1. Check the output bundles of a specific module from that scenario run. 2. See general information about the scenario run. 3. Switch between a simple log and an advanced log. ::Image[]{src="https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/YsunIPGQORwoIjm5NAg16-20260312-163804.png" size="70" width="2528" height="1070" position="center" darkWidth="2528" darkHeight="1070" showCaption="false"} ## Filter Scenario history To customize the columns you want to see in your Scenario history: ::::WorkflowBlock :::WorkflowBlockItem Click the filter icon on the right-hand side of the Scenario history. ![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/BG0KZ7WYBpbhdwKceR-TJ-20260313-090837.png) ::: :::WorkflowBlockItem In the dropdown, unselect the columns you want to hide. ::: :::: The **History** tab now displays only the selected columns. To hide change log entries or [check runs](docId\:BkdEyuBelio6YvvCosRxJ): ::::WorkflowBlock :::WorkflowBlockItem Click the three dots in the upper-right corner of the **History **tab. ::: :::WorkflowBlockItem Enable or disable **Hide check runs **and/or **Hide** **change log**. ![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/casIokyUBmk0zqYsCJ6Cv-20260313-091347.png) ::: :::: If you disable the check runs, the scenario history won't display scheduled scenario runs that check for new data, but don't return anything. If you disable the change log, the scenario history won't display any changes made in the scenario (e.g., edits, activation). ## Export Scenario history You can export your scenario history as a CSV file for a deeper analysis. To do that: ::::WorkflowBlock :::WorkflowBlockItem Click the three dots in the upper-right corner of the **History **tab. ::: :::WorkflowBlockItem Select **Export to CSV** from the dropdown menu. ![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/sDbvyjFjFEGE7m8bFcfyS-20260313-092156.png) ::: :::: The CSV file downloads to your device. It will include key scenario execution details like execution status, timestamp, author, operations count, execution duration, and the link to examine the execution. ## Full-text execution log search :::hint{type="info"} Available on **Pro** and higher plans. If you upgrade from lower tiers, Fulltext search will only display executions that were run after the upgrade. ::: Instead of going through the details of each scenario run entry one by one, you can use the **Fulltext search **to quickly find a specific entry. This feature lets you search for any term appearing in module outputs within the scenario execution history. :::hint{type="success"} **Example**: Suppose you ran a scenario that receives new registrations to the **Jotform > Watch for Submissions** module and adds registered participants to your database. If the scenario run was successful but a participant wasn't added, you can search for the participant’s name using the Fulltext search. This may help you quickly identify the issue and troubleshoot effectively. ::: To look for an entry in the **Fulltext search:** ::::WorkflowBlock :::WorkflowBlockItem In the** History** tab, click **Fulltext search.** ![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/BqtgtvOF2UsQPRGcsDk38-20260313-102055.png) ::: :::WorkflowBlockItem In the search box, enter the word or term you want to find. ::: :::WorkflowBlockItem Click the relevant search result. ![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/ZxrNLGDiVaTSZqqgNCO1w-20260313-102254.png) ::: :::: You’ll be redirected to the execution log containing the module and the bundle that includes your search term. From there, you can inspect the details.