# Logs

### What are Workflow Logs?

Workflow Logs provide a detailed, step-by-step record of everything that happens during a workflow execution. They capture the complete journey of your data through each step of your workflow, including:

* **Step execution details**: Runtime duration, success/failure status, and number of tasks processed
* **Input and output data**: The exact data that went into each step and what came out
* **Metadata**: Information about who ran the workflow, when it was executed, and from what source
* **Error messages**: Detailed error information when steps fail, helping you identify and fix issues

### Why Logs Matter for Your Workflows

* **Understand workflow behavior**: See exactly what data flows into and out of each step
* **Debug failed executions**: Identify where and why workflows fail with detailed error messages
* **Optimize performance**: Find bottlenecks by reviewing step execution times
* **Iterate without re-running**: Load any past execution into Studio with all outputs intact

<figure><img src="/files/vhAgpqWknB257AHCEbwg" alt=""><figcaption></figcaption></figure>

### Where to Find Logs

* **Studio Testing Mode**: Click on the History icon on the top right of the Studio to view the Logs that workflow's executions
* **Workflow History**: Access all past executions via the "History" tab in your workflow
* **Grid Workflow Columns**: Click any cell in the workflow column to view logs for that specific row's run

### Loading Executions into Studio

The **"Open in Studio"** button lets you load any previous workflow execution back into the Studio with all step outputs restored. This powerful feature enables you to:

1. Debug issues without re-running the entire workflow
2. Test changes using real data from actual executions
3. Skip waiting for external API calls or long-running processes
4. Iterate on prompts and logic with production data

To use it: Simply click "Open in Studio" from any execution's log view. The Studio will load with all intermediate outputs populated, allowing you to modify and test any step immediately.

This is especially valuable for debugging complex workflows, working with time-sensitive data, or collaborating on workflow improvements.

{% @arcade/embed url="<https://app.arcade.software/share/fc5g9N1qrk19HTAWNiKo>" flowId="fc5g9N1qrk19HTAWNiKo" %}

### Best Practices for Using Logs

1. **Use Descriptive Step Names**: Give your steps clear, descriptive names to make logs easier to navigate and understand
2. **Monitor Execution Times**: Keep an eye on step durations to catch performance degradation early

By leveraging the full power of Logs, you can build more reliable workflows, debug issues faster, and continuously improve your automation processes.


---

# Agent Instructions: 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:

```
GET https://docs.airops.com/actions/testing-and-iteration-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.