The main issue here is that the timing is alllll off. I’ve tried this a few different ways, all of which result in 1 of 2 results.
Result 1, the loading group is activated but then is not deactivated when the workflow/API are done processing. Mind you, the loading group becomes visible when the “current user’s is loading is yes”. In this result, the “current user’s is loading” is converted back to “no” at the end, but the group wont go away. Yes, the workflow that controls this is set to run every time, not just once.
Result 2, the entire process gets ran without the loading group ever displaying.
Methods used:
- Button is clicked, “current users is loading” is updated to “yes”, API is called, inside the external API is a webhook to reset the users loading to “no” as a last step. Result 1 is the outcome.
- Same as method 1, but with pauses between actions. Still get Result 1.
- Button is clicked, custom event is triggered to set “current users is loading” to “yes”. Next custom event is triggered to initiate the API. Result 2.
- No longer set “is loading to yes” inside bubble. Transfer this action to the API as a webhook at the beginning of the API (with and without a pause after this step). API completes by setting “is loading to no”. Result 2.
Now, regarding method 4, when this API is triggered manually from the third party, everything works as intended. Loading group appears, there’s a 5 sec delay, then the rest of the API goes off and the loading group disappears. There is something about bubble screwing this up, and something so simple shouldn’t be this difficult to accomplish.