I had built an availability calendar on my app using a string of custom events triggered by user’s selection of a date/time and frequency. Where one custom event would call another back and forth in a loop until a date stored as a state was reached. It was working fine.
Then today I logged in and saw a bunch of issues - looked closely and saw that every workflow event that called one of those triggers was no longer able to select any of my created custom events. None of my events are using API Workflow, just the regular on-page workflow.
Is this a temporary issue on Bubble, or was there a new release that made my workflow obsolete?
I agree it’s not the cleanest design, but from the forums it was the best way to allow users to create an “availability” calendar using only Bubble functionality. Otherwise I would have to build my own API/plugin from scratch.
I’m seeing the same issues as @projectvisionhealth now - I followed @DaveA’s calendar build (as I’m sure many others have too) and it was working great, not sure of another way to design the availability calendar at this stage. Certainly not the cleanest but it was working.
Are you guys still working on this or do I need to re-build?
A potential workaround is to turn this scheduling loop into an API workflow. I’m going to play around with it this weekend and post my results here + @DaveA’s original calendar post
Another potential workaround, if the list is small, is to have a sequence of calls to a custom event, and each one has a condition:
call the event, when count > 1
call the event, when count > 2
call the event, when count > 3
call the event, when count > 4
call the event, when count > 5
