> 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/ai-workbench-qore/console/flows/test-and-publish-flows.md).
# Test and publish flows
Run a flow with test data, respond to approvals, and publish a verified version.
Test a draft before publishing it. Review each task's result, resolve configuration issues, and then make the version available.
## Test a flow
{% stepper %}
{% step %}
#### Open Try Out
Switch from **Editor** to **Try Out**.
{% endstep %}
{% step %}
#### Provide input
Enter a value for every field in the input schema. Use **JSON Grid** for one field per row: select **+ Add Entry**, enter a **Key** and **Value**, then select **✓**. Or use **Raw** for JSON input.
Adding an input entry in JSON Grid.
{% endstep %}
{% step %}
#### Run and inspect
Select **Run**. The **Execution Log** records each task and its result. Before the first run, it reads *No execution logs available*.
Try Out.
{% endstep %}
{% endstepper %}
### Respond to an approval request
A **User Approval** task pauses the run. Enter the requested `answer`, such as `approve`, then select **Continue**. Select **Cancel** to stop the run.
## Publish a flow
Changes remain in a draft until you select **Publish**. Publishing makes the draft the current published version.
{% hint style="info" %}
**Validate before publishing.** Complete all required task settings and review the Execution Log for expected results.
{% endhint %}
## Manage versions and runs
| Area | Use it to |
| ------------------------ | ---------------------------------------------------------------------------------- |
| **Version History** | Review the draft, current published version, and earlier saved versions. |
| **Revert Draft Changes** | Discard the draft and restore the published version. |
| **Execution History** | Review every run by date, time, and status. Select a run to inspect task outcomes. |
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul AI-assisted, human-approved
{% endcolumn %}
{% endcolumns %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.uptiq.ai/ai-workbench-qore/console/flows/test-and-publish-flows.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
