--- title: "Using the Debugger for auto-start conditions" slug: "using-the-debugger-for-auto-start-conditions" description: "Diagnose flow issues with the Userflow Debugger. Learn to check Auto Start conditions and resolve triggering problems effectively." tags: ["Userflow Debugger", "Auto Start Conditions", "Flow Triggering", "Debugging Tool"] updated: 2026-11-13T16:29:34Z published: 2026-11-13T16:29:34Z canonical: "help.userflow.com/using-the-debugger-for-auto-start-conditions" --- > ## 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. # Using the Debugger for auto-start conditions The Userflow Debugger shows which auto-start conditions are stopping a flow from starting for a user. It runs from the Userflow Chrome Extension on a page of your app and shows each condition as passing, failing or waiting. If you're not sure this is a targeting problem specifically, start with the [Flow not starting](/userflow/docs/flow-not-starting) decision guide. ## Install the Userflow Chrome extension The Debugger is part of the Userflow Chrome extension. If you do not already have the extension, install it from the [installation page](https://chromewebstore.google.com/detail/userflow/ojbompffhdcndgndakoghndckimkohca). Setup steps are in [Installing the Userflow Chrome Extension](/userflow/docs/userflow-chrome-extension). If the extension doesn't open on your app, see [Chrome Extension not working](/userflow/docs/chrome-extension-not-working). ## Launching the Debugger > [!WARNING] > **Important** > > **You must be in your app when you launch the Debugger**. If you don't launch the Debugger while viewing your app, it may result in a *company not found* error. 1. Open your app. 2. While viewing your app, click the **Userflow Chrome extension** icon (if pinned) in your browser toolbar, or the **Extensions** icon, to open the Debugger. ![Userflow Chrome Extension icon in the browser toolbar](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(200).png) 3. Grant the logged-in user access, as described in [Granting Debugger access](/docs/using-the-debugger-for-auto-start-conditions#granting-debugger-access). ## Granting Debugger access ### Working with multiple environments in Userflow If you have more than one environment in Userflow for your app (e.g., staging and production), the Debugger will always redirect to your primary environment by default. To use the Debugger in a secondary environment, **first select the environment in Userflow,** then grant the user access. ![Environment selector in Userflow](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(213).png) ### How to grant access There are two ways to grant access to the Debugger tool for yourself or another user: - **Userflow Settings:** The best option when troubleshooting on behalf of another user. - **Debugger Tool:** The best option when troubleshooting with your own account. #### Userflow settings 1. Log in to Userflow and select **Settings > Debugger** from the sidebar. 2. Click **Add user**. 3. Enter the name, email, or ID of the user. *The list of users in the* ***Find user*** *dropdown menu contains all users who have access to your application. Either select from the list or do a lookup as you type.* ![Find user field in Settings > Debugger](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(199).png) 4. Click **Add user**. #### Debugger tool 1. Launch the **Userflow Debugger** via the Chrome extension. 2. Click the **Verify Setup** dropdown menu. 3. Click the **currently signed-in user** link. ![Currently signed-in user link in the Debugger's Verify Setup menu](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(202).png) 4. Click **Grant access in Userflow**. *This will redirect you to the* ***Debugger*** *settings page in the Userflow builder. If the signed-in user already has access to the Debugger, this button will not show up.* ![Grant access in Userflow button](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(203).png) 5. Click **Add user** and confirm that the **User ID** is correct. *The current browser session now has Debugger analysis capabilities enabled.* ![Add user confirmation with the user ID](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(205).png) ## Changing the user you're testing By default, the Debugger evaluates conditions for the user currently identified in your browser session: the user your app has called `userflow.identify()` with. To test conditions for a different user: ### Switch users in your app The simplest approach is to log out of your app and log back in as the user you want to test. Once your app calls `userflow.identify()` with the new user's ID, the Debugger automatically evaluates conditions for that user. Reload the Debugger to refresh. ### Verifying which user the Debugger is evaluating The Debugger displays the identified user's ID at the top of the panel. Check this before running a condition test. If the wrong user is shown, reload the page after switching users in your app. ## How do I check a flow's auto-start conditions? 1. With the Debugger open, click **Check auto-start** from the Debugger dropdown menu. ![Check auto-start option in the Debugger menu](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(207).png) 2. Select the specific flow you want to investigate from the **Select flow** dropdown menu. *Only published flows will appear in the list.* ![Select flow dropdown in the Debugger](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/image(206).png) ### What do the condition colors mean? Once a flow is selected, the Debugger displays its auto-start conditions as colored "pills". Each pill represents a condition or a group of conditions: | Color | Status | What it means | | --- | --- | --- | | 🔴 **Red** | Failing | This condition is blocking your flow from starting. | | 🟢 **Green** | Passing | This condition is currently met. | | 🔵 **Blue** | Waiting | This condition is waiting for an action or a time constraint (e.g., waiting for user input, waiting for time to elapse before re-triggering) | | 🟡 **Yellow** | Temporarily blocked | Temporary conditions are preventing the flow, often related to frequency or delays. Expand the pill to see the specific underlying conditions. | ### Conditions the Debugger checks The Debugger evaluates various conditions. Here are common issues that can block a flow: - **Attribute:** Checks if the current user or their company matches the specified User Attribute or Company Attribute filters. Requires attributes sent via Userflow.js, an integration (e.g., HubSpot), or the API. See [Standard Attributes](/userflow/docs/standard-attributes). - **Current page:** Checks if the user is on the specific URL path defined in the condition. See [URL pattern matching](/userflow/docs/url-pattern-matching). - **Event:** Checks if the user has performed the required tracked event. Events can be sent via `userflow.track` in Userflow.js or created using no-code Event Trackers. See [No-code event tracking](/userflow/docs/no-code-event-tracking). - **Segment:** Checks whether the user is currently in the specified Segment. See [Users and Segments](/userflow/docs/users-and-segments). - **Flow/Checklist:** Checks the completion status (e.g., Completed, Seen) of another specified flow or checklist. - **Element:** Checks if a specific UI element (identified by a selector) is present or has been clicked in your application. - **Text input value:** Checks if a form input field contains a specific value entered by the user. - **User fills in input:** Checks if the user has entered any value into a specific input field. - **Current time:** Used for scheduling flows. Checks if the current date/time is before or after the configured time. See [Scheduling](/userflow/docs/scheduling-userflow-experiences). - **Wait:** Checks whether the configured delay period has elapsed after all other conditions are met. - **Frequency of trigger:** Checks if the flow has already been shown based on limits like "Only show once" or recurrence settings. - **Delay Start After Previous Flow:** Checks if the required minimum time has passed since another specified flow was triggered. - **Constrain flow to current company (Advanced Setting):** If enabled, checks if the user's current company context matches the one they had when they first qualified for the flow. Prevents triggering if the user switches companies during a session. ![Debugger showing a flow's conditions as colored pills](https://cdn.us.document360.io/9697557a-eb5d-476f-9b09-062b0f7bdcbd/Images/Documentation/debugger-02.png) ### Which flow starts when several match? When several flows meet their auto-start conditions for a user at the same time, Userflow starts one: the flow with the highest **Priority** (set in the flow's settings). If they share the same priority, the flow created first starts. For examples and how to control the order, see [Flow priority in How to start flows or checklists](https://help.userflow.com/docs/how-to-start-flows-or-checklists#flow-priority). ### Fix a condition that's blocking a flow Once the Debugger shows you the specific red condition(s) blocking the flow, you can: - Adjust the auto-start conditions of the flow in the Userflow builder to better match your requirements. - Verify that the required user attributes, events, or page states are implemented correctly in your application. After making updates, re-check the conditions using the Debugger to confirm the pills turn Green and the flow triggers as expected. ## Why isn't my flow in the Debugger's list? When you open **Check auto-start**, the Debugger shows the flows currently eligible to start on the page you're viewing. This list is limited to flows that: - Are published in the current environment - Have auto-start conditions configured - Are not blocked by frequency rules for the current user If a flow isn't appearing in the list: 1. **Confirm the flow is published in the correct environment.** Open the flow in Userflow and check its publish status. 2. **Check frequency rules.** If the current user has already seen the flow, it won't appear in the Debugger's auto-start list. To test: go to **Users → [User] → Sessions** and [delete the session](/userflow/docs/deletingresetting-user-data) for that flow. Then reload the Debugger. 3. **Confirm the flow has auto-start conditions set.** Flows without any auto-start conditions must be started manually and don't appear in the auto-start test list.