i have a thing going on that i don’t understand. this is a repeating group showing 1 item at a time. When clicking on 0,1,2 the next item is shown and the value is saved to the database.
unfortunately when I click through the list really fast. The numbers don’t get saved to the database.
The workflow looks like this:
When in debug mode step by step, everything is fine. The error / bug only ocurres when clicking through the list real fast.
Any idea how to prevent this or make the workflows more robust?
I tried saving the data through triggering a custom wf (which should (when I understood correctly according to bubble wf execution tutorial https://www.youtube.com/watch?v=IbhCrciOKHM prevent the rest of the wf of its execution) I also implemented a only when data is in parent group data condition (I gues this field would be empty because data has not been passed to the element when I am clicking real fast)
This is probably happening because your second click (or some of them) is happening while your application is still processing your workflow. This is something you need to click really fast??
What you can do to prevent this behavior is:
Create a Custom State in your buttons called “Loading” (Type Yes/No);
Create a condition in all the buttons to make the button not clickable when Loading = Yes;
In the first step of your workflow change their custom states to “Loading = Yes”;
In the last step of your workflow change their custom states to “Loading = No”;
This will prevent users to keep clicking the buttons while your workflow is still running…
Hi @rpetribu thanks for your idea. Unfortunately, this is not working for my case. According to my interpretation of bubbles workflow execution rules you cannot be sure that the workflow will get triggered sequentially. i also tried putting the set to no in a custom workflow.
I am 100% sure that this is going to work as expected, did you already tried?
Edit:
Also… what you can do is… you are making a change in some field of your “ET_Questions_BETA”, so in order to force the action that will change your custom state back to NO (Loading = No) to run in the end of your workflow, you can make a condition in this step (Only When) to run the action only when the field you are editing in Step 1 in not empty anymore…
when checking the logs i saw that the there where 4 workflows triggered from the same unique id. so this might caused skipping 3 item of my list. this would be possible because the conditions (loading=yes) would be true when clicking really fast. I know this is not likly to happen…
my current workaround is triggering the next item workflow from another button that shows up when clicked on the number…