Hi Bubblers,
I’ve been lucking on the forum for the past month and soaking in a lot of great tips. I have a design question related to scheduling events so it’s time for my first post.
I’m using Bubble for a startup MVP and eventually for our initial deployment.
App overview:
The easiest way to describe the components I’m working on now is like a scheduled survey engine.
Entities: a “user” is a member of a “program” which has a nested structure of entities including type of “topic” Each “topic” has multiple “questions”. "Topics have a defined schedule they are due “day of week”, “time”, and “frequency”.
The end goal of all of this is to have a daily SMS message go out to every user based on the data collection that is due that day. These are tracked as “requests” so I know when they were triggered and link any actions and “responses” to this record.
Objective: Trigger multiple SMS messages daily based on user, program, and topic scheduling data.
Question: I can see multiple ways to tackle this. I’m looking for advice from people that have worked with the scheduling engine to identify the best practice approach. I’m also trying to not exceed the limits of scheduling event frequency so I can stay in the pro license tier.
Options I’m thinking of so far:
- A daily workflow that queries tables and generated a list of scheduled events for every user’s request for that day.
- Queue a single request event for each user for the next request that is due. During the processing of that request, calculate and generate the scheduled event for the next request.
I’m open to any and all options. I’d also appreciate any concerns and pitfalls I should be on the look for.
Happy to share more detail or take the discussion offline if that’s easier.
Thanks for your advice.
John