> For the complete documentation index, see [llms.txt](https://docs.automateo.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.automateo.app/execution-history.md).

# Execution History

Automateo provides detailed execution history for each of your workflows. To access this information:

1. Navigate to your workflow dashboard
2. Select the workflow you want to analyze
3. Click on the "Details" tab

In the execution history, you can view:

* Execution timestamps: When each run of the workflow was triggered
* Input values: The data provided to the workflow for each execution
* Output results: The final output of the workflow
* Amount of tokens: How many input and output tokens were used
* Runtime duration: How long each execution took to complete
* Average cost: The estimated cost per execution based on the models used
* Even more details: Click the "View Execution Details" button to see a step-by-step inputs and outputs

This information is valuable for:

* Debugging your workflows
* Optimizing performance
* Tracking usage and costs
* Ensuring reliability of your AI processes


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.automateo.app/execution-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.