Execution History
Last updated
Last updated
The Execution History page is where you can review all the past executions of your automation flows in Otomato. This page helps you track, analyze, and understand the outcomes of your automated strategies.
Overview of the Page
The Execution History page is designed to give you a clear and organized view of every flow that has been executed. Each execution is listed with essential information, allowing you to quickly assess the success or failure of your automation.
Key Features
Execution Status:
Correct: This status indicates that the execution was successful and all actions were performed as expected.
Error: This status shows that there was an issue during execution, and the flow did not complete successfully.
Date and Time:
Every execution is timestamped, showing the exact date and time it occurred. Executions are listed in chronological order, so you can easily see the most recent activities at the top.
Seen/Unseen State:
Just like emails, each execution has a "seen" or "unseen" status. Unseen executions are highlighted to draw your attention, ensuring you don’t miss any new or unreviewed executions.
Grouping and Sorting Options
To help you manage and navigate through your executions, the page offers flexible grouping and sorting options:
Order by Execution Time: You can sort the list by the time each flow was executed, making it easy to follow the sequence of events.
Group by Flow: Alternatively, you can group executions by the specific flow they belong to. This allows you to see all executions of a particular automation in one place.
Detailed Execution View
When you click on an individual execution, you’ll be taken to a more detailed view. This can either be a full page or a popup, depending on your settings:
Trigger Information: This section displays the specific condition or event that triggered the automation. For instance, if a tweet or market change initiated the flow, the details will be shown here.
Wallet Movements: You’ll see a detailed list of all transactions related to the execution. For example:
100 USDC → 1400 USDC
1400 DOGE → 106 USDC
Transaction Hashes: Each transaction includes a hash, which is linked to a blockchain explorer. This allows you to verify and explore the transaction directly on the blockchain.
