--- title: "Automations run history" slug: "automations-run-history" updated: 2025-12-23T20:04:21Z published: 2025-12-23T20:04:21Z --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Automations run history *Learn about run history and how you can use these insights to invoke changes in your automation.* Run history shows the archive of all the Runs an Automation has completed. A run refers to each time an event is invoked. For example, when a Machine outputs or when a Table Record is created or updated. The run history of an automation reveals the status of the automation, i.e., whether or not it is successfully running and triggering from an event. The log of runs is kept for 6 months, after which runs will be deleted from the history. If you are on a release before January 2025, the run history will only show the previous 3 days. Note Run history will take 6 months to populate after Jan 2025, it will not pull the previously deleted data. ## View run history There are two ways to view the run history of an automation. 1. **Logic Editor panel** of the Automations Editor ![Automations Run History1](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Run%20History1.png) When no Logic Block is selected in the Automations Editor, you can see the most recent run history of the current version. 2. [**Run history page**](/r230/docs/automations-run-history#run-history-page) The run history has more details than the Logic editor view. This page shows the history for all versions of the automation, up to 3 days. ## Run history page To access the run history page, click on the automation you want to view and then click the **Run History** tab. ![Automations Run History Annotated](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Automations%20Run%20History%20Annotated.png) The run history page is dedicated for viewing the status of automation runs. The data includes the version number of the automation, the status of the run (see [Run states](/r230/docs/automations-run-history#run-states)), and the datetime that the run started and ended. You can use this page to gather insights and determine if you need to edit the automation for optimal use. ![Screenshot 2024-04-25 at 11.41.09 AM](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202024-04-25%20at%2011.41.09%20AM.png) The run history also provides insight into why an automation run may have succeeded, failed, or been limited. The history shows the completed steps or the available error message. ### Run states There are 4 different states for each automation run: | State | Description | | --- | --- | | ![success](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/success.png) | Success - the automation ran without issue. | | ![time out](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/time%20out.png) | Timed Out - the automation ran until it hit its time limit (learn more [here](/r230/docs/automation-limits)). | | ![limited](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/limited.png) | Limited - the automation was either called too many times (see this article) or your workspace is at its limit for automation runs per second (see this article, [Automation Limits](/r230/docs/automation-limits), for additional information). | | ![failure](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/failure.png) | Failure - the automation ran into an issue - the automation will describe the issue or have internal error listed, if so, please reach out to support. | ## Debug an automation with run history The run history will indicate the type of issue that occurs with an automation, but you will need to investigate to understand the root cause. ### Example 1: Limited The run history identifies if a rate limit was reached, but does not specify which limit. If a run state is "Limited", you can identify the most appropriate [Automation limit](/r230/docs/automation-limits) relevant to your automation by troubleshooting each limit. ### Example 2: Timeout The run history identifies if a timeout occurred, but does not specify the logic during which the automation timed out. You can examine the logic in your automation and determine if you have multiple "slow-running" logic blocks, such as Run connector function or Create/update a table record. These types of logic take longer to execute and, therefore, risk reaching a timeout. You can reconfigure the automation logic to avoid this risk. ## Further Reading - [Getting Started with Automations](/r230/docs/getting-started-with-automations) - [Overview of the Automations Editor](/r230/docs/overview-of-the-automations-editor) - [How to Use Automations Versions](/r230/docs/how-to-use-automations-versions) --- Did you find what you were looking for? You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have solved a similar topic! **Run** Occurs each time an event is invoked in an **automation**. **Automation** **Workflow** that performs tasks in the background, without an interface. Automations run logic every time an **event** occurs. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Glossary/Automations1.gif) **Machine** A **Machine**is a digital representation of a physical datasource. Machines have **Attributes**that are updated through an OPC-UA Connector or the Tulip API. **Table Record** A **Table Record** is a reference to a row in a **Tulip Table**. Table Records can be created either from the Table UI or from with an App Trigger. To edit a record it must be loaded into a **Table Record Placeholder.** **Logic Editor** Visual editor for managing and creating logic for **Automations**. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Glossary/Automations%20Logic%20Editor.gif) **Automations Editor** Visual editor for managing and creating **automations** within the Tulip platform. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Glossary/Automations%20Editor.png) **Logic Block** *Event*, *action*, or *decision* in an **Automation**.