Troubleshooting

If a flow isn't behaving as expected, work through these common causes first.

A flow isn't showing

• Is it published? Only published flows show to users. Check the flow's status in the flows list.
• Does the page match your targeting? Open the flow's Targeting and confirm the current page and user meet the conditions. Empty targeting shows to everyone.
• Has this user already seen it? By default a finished or dismissed flow does not auto-show again. Use onbixo.reset(flowId) in the console to re-test.
• Is the domain allowed? The runtime only serves flows on your allowed origins. Add the domain you are testing on.
• Is the snippet installed on this page? Confirm the script tag is present and window.onbixo exists in the console.

A step points at the wrong element (or nothing)

• The target element may not exist yet when the step runs, or its selector may have changed. Re-capture it with the extension, or type a more stable CSS selector.
• If an element cannot be found, the step is skipped rather than breaking the flow.

Targeting on traits isn't working

Trait and event conditions need data. Make sure you call identify (for traits) and track (for events) before the flow evaluates. Page, device, and country conditions work without identify.

My changes aren't live

Edits save to the draft, not the live flow. Click Publish to push them live. A "Unpublished changes" pill means your draft is ahead of what users see. See Draft, publish, archive.

New users stopped seeing flows

You may have reached your plan's monthly active user cap. New users beyond the cap stop seeing flows until the next month; upgrade for a higher cap. See Plan & billing.