# Debug workflows

When workflow delivers poor results, you need to figure out, what happened.

Poor results may happen due to 4 cases:

1. Poor input data
2. Poor data from public sources
3. Poorly formatted prompts
4. Poor workflow design

Every case has its own solution, but you need to find a reason first.

Debug lets you do that.

## How to use Debug in Drafter AI:

Every workflow block has a <mark style="color:blue;">**"Debug"**</mark> view after you tried to execute the workflow.

By clicking it you get access to a JSON view of all the inputs and outputs that were processed in the specific AI block during the last workflow run.

It lets you understand, at what point something went wrong, and make relevant changes.

{% hint style="info" %}
Flow controls and inputs don't have a "Debug" view.
{% endhint %}

See, how to use it:

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


---

# 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.drafter.ai/maintain/debug-workflows.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.