How does Bubble use objective time?

If a tree falls in the forest does it make a sound? In my short experience with Bubble, the tree doesn’t even fall.

I’m looking to create a countdown timer that performs actions on things whether a user is present or not. Unfortunately, things that have workflows associated with their countdown timer only obey when a user is present on the app.

To visualize this, pretend users pre-pay for electronic billboard space. Each hour costs $1. Their content should play at designated time slots and change on the hour regardless if someone is there to observe it.

I understand that Bubble uses javascript time and that is calculated in increments of date. But I haven’t found out how to make time work objectively in the app yet. Any pointers? Thanks!

Hey @adam27

Why don’t you create an option set with a time field and save the end time in there? You can then reference that from the front end to calculate how much time is left, but also show underneath say the end time as an actual date & time formatted in the users timezone if needed. You can also reference this option set in backend workflows to do things while a user isn’t present, as long as the workflow has been triggered at some point (could even be a button on an admin page).

The only thing I’m unsure of (might be worth a test) is that if backend workflows timeout at any point. I’ve had them timeout when I’m doing heavy lifting with an external API doing things. But I’m not sure what would happened if you triggered a workflow today that then went on to do something when the time in your option set hit 3 days from now. In theory it should work?

Josh @ Support Dept
Helping no-code founders get unstuck fast :rocket:save hours, & ship faster with an expert :man_technologist: on-demand