Publishing
==========

Publishing an Agentic Flow makes a specific version available to live channels and API callers.

.. image:: ../images/agentic-publish.png
   :alt: Agentic Flow publish flow — validate, review, publish
   :align: center
   :width: 100%

| The publish flow follows a validate → review → publish sequence, identical to the Chatbot publish flow.

Versioning
----------

Every time a flow is approved through the review process, a new numbered version is created. The version dropdown in the header (e.g. **v1.0**) shows the currently active version.

To view or restore a previous version, click the version history button in the header. Selecting a past version loads it in read-only mode. Click **Restore** to make that version the working draft.

Publish Flow
------------

Publishing requires edit mode to be active. The steps are:

1. **Validate** — click the publish button (top-right header) and select **Validate**. The system checks the flow for configuration errors. The result is shown as Valid or Invalid with a timestamp.

2. **Request Review** — once the flow is valid, click **Request**. This submits the flow for approval and sets the status to **Pending Approval**. The flow is locked for editing until the review is complete.

3. **Review** — a user with approval permissions sees a **Review** option in the publish menu. They can add an optional comment, then click **Approve** or **Reject**.

   * **Approve** — creates a new version and makes it the active draft, ready to publish to channels.
   * **Reject** — returns the flow to **Available** status with the reviewer's comment. The builder can make changes and request review again.

4. **Publish to EKS** — after approval, click the publish button and select **EKS** to deploy the approved version to the live environment.

Edit Mode
---------

Only one user can edit a flow at a time. The edit mode toggle in the header shows whether you currently own edit access. If another user has the flow locked, the header shows their name and the time they took ownership.

Users with the appropriate permission can unlock a flow locked by another user.