> For the complete documentation index, see [llms.txt](https://docs.flxbl.io/flxbl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flxbl.io/flxbl/codev/flows/overview.md). # Flows The Flows section is where you track what codev is doing, approve release requests, and turn individual flows on or off. ## Runs
The Runs page

The Runs page showing flow executions across every category, with status and timing

Every action codev performs — building packages, deploying to a sandbox, releasing to production, refreshing a pool — runs as a **flow**, and this page lists all of them. Use it to: * **Check if a deployment finished** — filter by status to find completed or failed runs. * **Debug a stuck run** — a "Waiting" status usually means the run is at an approval gate; check **Pending Approvals**. * **Investigate a failure** — open the run to see which step failed. You can filter by category (build, release, pool, sandbox), task type, who triggered it, and status. ### Run details
A flow run's detail page

A run's detail page — sub-flows on the left, step-by-step logs on the right

Opening a run shows everything about that execution: its status and elapsed time, what triggered it (a push, a comment, a schedule), the commit it ran against, and its sub-flows. The log pane breaks the run into its steps — for a build on merge, that is detecting impacted domains, building each domain, and deploying to environments — and you can open any step to read its full log. From here you can also retry a failed step or re-run the whole flow. ## Pending Approvals
Pending Approvals page

The Pending Approvals page showing release requests awaiting review

When someone requests a release, it does not deploy immediately. The request enters an approval gate and appears here. Each request you are authorized to resolve shows an **Approve** and a **Reject** action: * **Approved** — codev locks the target environment, deploys the packages, and unlocks it. The release appears on the [Releases](/flxbl/codev/ci-cd/overview-3.md) page. * **Rejected** — the deployment is cancelled. The release candidate remains available for a future attempt. If the release targets multiple environments, each environment has its own approval request — approving the staging deployment does not approve production. A request that nobody resolves expires (60 hours by default) and does not deploy. For how the approval gate works, where requests appear, who can approve, separation of duties, and gating on a ServiceNow change request, see [Approvals](/flxbl/codev/governance/approvals.md) and [Configuring approval gates](/flxbl/codev/governance/approval-gates.md). ## Configuration
Flow configuration

Turning individual flows on or off for a project

codev ships with built-in flows for common operations — building on merge, validating and analyzing pull requests, creating patch branches, syncing environments, and more. The **Configuration** page lists every one of them and lets you turn each on or off for a project. Disable a flow when you don't need it, or when you are replacing it with your own automation — a GitHub Action, an Azure Pipeline, or an external job (bring your own workflow). A disabled flow does not run through any route: it is not triggered by a webhook, a schedule, or a manual run. This switch is project-wide. To keep a flow on but skip it for certain branches — for example, build on merge to `main` but not to your `release/*` branches — use the **Workflow Settings** dialog on that flow's own page instead, which filters by branch rather than turning the flow off everywhere. ## Related * [Approvals](/flxbl/codev/governance/approvals.md) — resolving requests, who can approve, expiry * [Configuring approval gates](/flxbl/codev/governance/approval-gates.md) — which environments require approval and separation of duties * [Managing Release Candidates: Requesting a release](/flxbl/codev/ci-cd/managing-release-candidates.md#release) * [Releases: What is deployed where](/flxbl/codev/ci-cd/overview-3.md) --- # 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.flxbl.io/flxbl/codev/flows/overview.md?ask=&goal= ``` `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.