Hello everybody!
From what I’ve noticed, when I trigger a custom event that has a check in the “only when” field to verify if the user is logged in, all actions seem to wait first for the verification to be true before being executed. And it doesn’t matter if triggering the custom event action is the last step because the first one will be slow. More details below:
I created a workflow for a button to close a popup, and in the next step, it triggers a custom event that updates a client’s field. So far so good; the workflow hides the popup at lightning speed and updates the client’s name.
Problem: I created another button and replicated the same situation. The difference is that, in the custom event, I added a condition (in the ‘only when’ field) to check if the user is logged in. Now, when clicking the button, the first step (hiding the popup) experiences a delay.
Apparently, the delay is caused by the condition I added in the “only when” field of the custom event, although I’m trying to understand how this affects the step of closing the popup since it occurs before the condition check of the custom event. If I remove the condition, everything goes back to normal.
Editor: Laboratoriosemcodar | Bubble Editor
Page demonstrating the popup closing delay: Teste Popup (bubbleapps.io)
