> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/console/flows/flows-faqs-and-troubleshooting.md).

# Flows: FAQs & Troubleshooting

Find answers to common flow questions and resolve known configuration and test issues.

This page answers common questions about building and running flows. Use the troubleshooting steps when the product shows a specific status or warning.

## FAQs

<details>

<summary>Where can I use a flow?</summary>

A flow belongs to the project where you create it. It is not available in other projects.

</details>

<details>

<summary>How do I start a flow?</summary>

Choose a trigger:

* **Start manually** starts the flow when a user launches it.
* **Start through Agent** lets an AI agent start the flow.
* **Start via trigger** starts from an external event. This option is still in development.

</details>

<details>

<summary>Can an agent use a flow?</summary>

Yes. Each flow is available as a skill with the flow's name and description. Add it through the agent's **Add Skill** dialog, or use the **Start through Agent** trigger.

</details>

<details>

<summary>How do I provide input to a flow?</summary>

Define fields in **Input Schema**. During **Try Out**, provide a value for each field. You can enter values in **JSON Grid** or as raw JSON.

</details>

<details>

<summary>How do I protect credentials?</summary>

Store API keys, tokens, and other credentials as **Secrets**. Reference them in task settings with `$secret.{variable_name}`.

</details>

<details>

<summary>When do changes become available?</summary>

Changes remain in a draft until you select **Publish**. Publishing makes that draft the current published version.

</details>

## Troubleshooting

<details>

<summary>A task shows a red warning icon</summary>

A required task setting is empty. Select the task, complete the required setting, and test the flow again before publishing.

</details>

<details>

<summary>The flow pauses during a test</summary>

The run may be waiting at a **User Approval** task. Enter the requested `answer`, then select **Continue**. Select **Cancel** to stop the run.

</details>

<details>

<summary>A test result is not what you expected</summary>

Open **Execution Log** after the run. It lists each task and its result. Review the input values and task configuration, then run the test again.

</details>

<details>

<summary>I need to undo draft changes</summary>

Open **Version History** and select **Revert Draft Changes**. This restores the published version.

</details>

{% hint style="info" %}
**Need configuration details?** See [Build a flow](/console/flows/build-a-flow.md) and [Test and publish flows](/console/flows/test-and-publish-flows.md).
{% endhint %}


---

# 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.uptiq.ai/console/flows/flows-faqs-and-troubleshooting.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.