--- title: "userflow-flow-review" slug: "userflow-flow-review" description: "Userflow flow review finds and prioritizes live flow blockers using settings and 30 days of data, with actionable fixes before users encounter problems." tags: ["Flow Review", "Userflow Diagnostics", "Onboarding Flows"] updated: 2026-11-17T16:04:27Z published: 2026-11-17T16:04:27Z canonical: "help.userflow.com/userflow-flow-review" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.userflow.com/llms.txt > Use this file to discover all available pages before exploring further. # userflow-flow-review Finds the problems in your flows before your users do. Reviews all your live flows, or the ones you name, and gives you a prioritized list of what stops each one from starting, showing its tooltips or letting users finish—with a fix for each. ## Download [](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/userflow-flow-review.zip)userflow-flow-review38.18 KB[](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/userflow-flow-review.zip) ## What it does The skill reads each flow's start rule, page rules, steps, tooltip targets, step triggers, buttons and hand-offs to other flows, and checks them against how Userflow actually decides when a flow starts, shows and finishes. It then looks at the last 30 days of live data—views, where people drop off, and "element not found" events—so a finding is backed by what real users saw, not only by the settings. It works the same for flows built in the Builder and flows created through the Userflow MCP, so it's also a good check right after an AI tool creates or edits a flow for you. You get a report ordered by what matters most: - **Blockers**—problems that stop a flow from ever starting, showing or finishing, such as a hidden step users can never leave. - **Should fix**—problems that break the flow for many users or in specific situations, such as a button that starts a flow that isn't published. - **Worth a look**—risks and questions, such as a tooltip target that tends to break when your app's wording changes. - **Can't check from here**—the few things the skill can't see, asked as questions, each with a link to the help page that explains it. When it reviews several flows, it leads with a table sorted by the worst problem and then by views, so the problems that reach the most users come first. Flows that share the same problem are grouped into one item, and stale flows—live for more than 30 days with no views or no completions in the last 30—get their own short list. ## What you'll need - The [Userflow MCP](https://help.userflow.com/docs/mcp) connected ## How to use it - "Find any problems with my live flows and prioritize them." - "Why isn't my onboarding tour showing for anyone?" - "Check the flow I just created before I publish it." - "Review all flows labeled Onboarding." If you don't name a flow, it reviews every flow that's live in your Production environment. You can also name flows, paste their Builder links, or describe a set, such as all drafts or a label. Describing a symptom, like "the tooltip on step 3 keeps disappearing," makes the skill lead with the checks that explain it. If you have more than 50 flows, it tells you how many there are and asks which ones to review—for example only published flows, flows with unpublished changes, a label, or recently edited ones. ## What it covers Flows, both single-step and multi-step. Checklists, launchers, banners, announcements, resource centers and the Adoption Agent are left out. ## Things worth knowing **It never changes anything.** The review is read-only: it doesn't edit, publish or unpublish flows. If you ask it to apply a fix afterwards, it tells you exactly what will change and waits for your OK. **Steps are read from drafts.** The skill can read only the latest draft of a flow. If a flow has unpublished changes, findings from its steps are marked "in your unpublished draft, not live yet," so you know your users aren't affected yet. Findings from live data always describe the live version. **It can't see your site.** Your Userflow.js installation, your theme's setting for missing tooltip elements, and the checklist or launcher that starts a manual flow aren't visible to it. Instead of guessing, it asks you about them. **Guesses are asked as questions.** Anything the data shows plainly is reported as a finding. Anything that's only a risk is phrased as a question, so you can confirm it before acting on it. **Big reviews take a few minutes.** Each flow is read one by one. With more than 20 flows, the skill tells you up front that the review will take several minutes and use a fair share of your plan's usage. **Zero views isn't always a problem.** A flow started by a checklist or launcher only gets views when something starts it. The skill tells you nothing is starting it and asks what should. ## What to do with it Start with the single most important fix named at the end of the report, then ask the skill to review the flow again once you've made the change. Flows break when your app changes, so it's worth running the same review weekly or every two weeks. The skill offers to set that up if your AI tool supports scheduled tasks, and a scheduled review only reports—it never changes your flows. ## Related - [MCP write tools: create flows, segments, and charts from your AI tool](/mcp-write-tools.md) - [userflow-optimize-autostart](/userflow-optimize-autostart.md) - [userflow-create-reactive-flows](/userflow-create-reactive-flows.md)