When a workflow has a condition that prevents it from running, Bubble may still evaluate some of the data sources needed by the workflow's actions on the client side. If any of those data sources require a browser permission — like the user's current location — the browser may prompt for it even though the workflow doesn't ultimately run.
What you might notice
A browser permission prompt (such as a location request) appears even when the workflow's condition isn't met
The workflow itself behaves correctly — only actions with passing conditions execute
Data may be fetched in the background even though it isn't used
Workaround
Where possible, restructure workflows so data sources requiring permissions are only evaluated when the condition is likely to pass. Moving data-fetching logic into custom events or backend workflows can help avoid unnecessary client-side evaluation. The actual workflow execution is unaffected — this is only a data-fetching side effect.