---
title: "Publishing Flows"
icon: 'bolt'
description: "Make your flow work by publishing your updates"
---

The changes you make won't work right away to avoid disrupting the flow that's already published. To enable your changes, simply click on the publish button once you're done with your changes.

![Flow Parts](/resources/publish-flow.png)

By default, publishing also turns the flow on. When the flow is already live, the new version replaces the old one on the same trigger, so a webhook flow keeps its URL. On a self-hosted instance that sets [`AP_ENABLE_FLOW_ON_PUBLISH`](/install/reference/environment-variables) to `false`, publishing turns the flow off instead; turn it on with its switch.

<Info>
In projects marked as **Sensitive**, publishing requires review from a user with the `PUBLISH_SENSITIVE_FLOW_ACCESS` permission. The Publish button reads **Request approval** instead. See [Flow Approvals](/flows/flow-approvals) for how the gate, review workflow, and audit trail work.
</Info>

## Turn a flow on or off

Use the switch next to the flow, in the builder or in the flows list. A flow that is off ignores its trigger: a call to its webhook answers `404` and starts no run.

A flow that was never published has no version to run, so its switch stays disabled until you publish it.

## When publishing fails

When the trigger refuses its settings, for example a schedule with an invalid cron expression, the builder shows **Publish failed** with the reason the app reported. The flow stays off until a publish succeeds, also when an older version was live before. Fix the trigger and publish again.