Condition Triggering When It Shouldn't Be

[ericdf94]

Hi, I have a workflow for making a “page” on my Bubble site that checks some things and then makes it. It checks if the name is taken, the length, no spaces, etc and if it is valid, it creates the page.

I was messing around with a limit on pages as a possible paid feature so to test I just let the limit to 1. I tested a user with 0 pages making a page with valid name and everything works fine except the alert I made as an error message. It is only supposed to show if they already have a page created but it shows even it is the first page. It shares the same conditions as the terminate workflow right after it but the workflow makes the page successfully and also shows the error message.

Is it possible that when the page is created in the later steps it is causing the message from earlier to pop up?

Here is what the workflow looks like https://i.imgur.com/4HBkebA.png

Any help is appreciated.

[cmarchan]

If any of the terminate workflows trigger … that is it … the workflow ends

[ericdf94]

Yea, the problem is the alert right before the terminate workflow has the same conditions. The alert triggers but the terminate doesn’t, it goes to completion.

[hanan1]

Maybe if you state it in other words; maybe use the result of the alert step as a condition for the terminate workflow step since the alert does show so the condition is true at least for that step regardless what happens later. Just thinking.