PRODUCT GUIDE
Manage your flows
Understand approval, boundaries, re-authoring, and suspended coverage.
01A flow is an approved user journey
A flow describes a sequence of browser actions and checks. Review the plain-English steps first; technical selectors and matching details are available when you need them.
Drafts do not run as approved coverage. A proposal that needs input stays distinct from an active flow until its missing requirements are completed and it is approved.
02Update coverage
Use Add a flow to discover additional journeys on an existing repository or describe a journey. Use re-authoring when a substantial UI change calls for fresh steps; review the proposed replacement before approving it.
Run now checks a flow against the selected preview without creating a pull-request check. The resulting run remains available for inspection.
03Suspend and reactivate
Suspended flows retain their definitions and history but do not run as active coverage. Reactivation follows the same plan and overage constraints as approval. Pin the flows you want to keep when your plan decreases.
Ready to put it into practice?
Open your workspace, or walk through setup with the founder.