Your backend workflow is set up correctly so there’s no issue there.
But it looks like you have some errors in the way you’re triggering the workflow to run.
Without knowing more about your app’s datastructure, and exactly what you’re trying to do I can’t say exactly what will work for you, but here are a few things I notice…
Firstly, you’re using a ‘do when condition is true’ workflow in the browser to trigger the backend workflow. That will only work when the user’s browser is open. So unless your users keep their browser open and logged in to that specific page 24/7 it’s not going to work reliably to trigger a backend workflow such as yours.
Also, the standard Bubble current/date time doesn’t update in real time, so you can’t use a ‘do when condition is true’ to trigger something based on a time changing or updating.
Besides, if you’re scheduling a backend workflow to run at a specific time, it doesn’t make much sense to trigger that workflow at that exact same time (if you want to do that you can just schedule it for ‘current date/time’ instead so that it will run immediately, or even not bother with a backend workflow at all - just run a browser workflow to run the actions).
In terms of who the workflow is running on, again I don’t know how your database is set up or who exactly you want the workflow to run on, but you’re currently running the workflow on the current page group’s members.
So if it doesn’t appear to be running on all of the users you want it to be then it’s probably either down to how you’re selecting and filtering that list, or it’s to do with the various conditionals you’ve got on the workflows and actions. So either check how you’re selecting the list to run it on, check your database User entries, or rethink what conditionals you need/don’t need and how you’re setting and resting those fields.
Again, without knowing your app I can’t be specific, but from what I’ve seen it looks as though the best way to achieve what (I think) you’re trying to achieve would be to schedule the backend workflow to run on the date of the game whenever that game is created.
So wherever/however you add ‘games’ to your database, in that same workflow schedule the backend workflow to run on the date of that game, on whatever list of users it is that the workflow needs to be run on.
Be aware though, that when you schedule a workflow to run on a list on a future date, you’re scheduling it to run on that list as it exists at the moment you schedule it, NOT what it may look like at the time it’s scheduled for.
In other words, if you schedule a workflow to run in a week’s time on a list which contains 100 users at the time you schedule it, then another 50 users are added to that list before the scheduled date arrives, the workflow will only run on the original list (of 100 users) it was scheduled for.
So you’ll need to add an extra backend workflow to schedule the other one for the ‘correct (current) list’ if you want it to run on the list as it exists at the time it runs.
