Execution history
Learn about the importance of automation execution history and its retention in this informative document. Discover how the number of processed, filtered, and errored data rows are recorded and stored, along with billing units for subscription plans. Expl
Each time an automation is executed, the results of the execution are recorded in its execution history:
Each entry records the number of successfully processed, filtered, and errored data rows.
If the account has a subscription plan, a count of the plan's billing units is also displayed. The default billing unit is "task", which is a count of how many non-system actions were executed. In this example, the billing unit is "Booking":
If the account has the "Assembly Developer" or "Switch Account" permission the "eye" icon at the lower right will provide access to stored history information:
Execution history is searchable. Simple AND/OR logic can be used:
In this section
Drilling into execution history
Learn more about the "Execution history" screen and how it provides an overview of automation executions. Discover how to access details and view processed data rows for each execution. For a deeper understanding, refer to the comprehensive "Data row hist
Retrying multiple errors
Learn how to use the "Errors" filter in the execution history screen to easily identify and resolve errors in your document. With the "Retry all errors" button, you can efficiently retry failed transactions based on your search and date criteria. Choose b
Searching execution history
Learn how to effectively search the execution history of a system using search terms and advanced filters. Discover how to use AND/OR logic for search phrases and filter your results based on different criteria such as success/errors, awaiting form submis