Editor
Demo
Hey everyone! I’m releasing a new plugin that let’s you add pauses in between workflows. It will be aptly named “Wait Please” 
Benefits:
Wait until some time has passed before executing an action. Avoid unnecessarily complex conditions & workflows.
Works with Backend workflows 
Works with Frontend workflows
Facilitates maintainability
Instructions and specifications
First things first, decide whether or not to use Wait - Client Side or Wait - Server Side. Both actions have their own benefits.
Why use Wait - Client Side?
Disadvantages:
a. Cannot be used in Backend workflows
Why use Wait - Server Side?
Disadvantages:
- Shows a progress bar at the top of the window
Setup: Wait - Client Side 
-
Place “Wait” element on the page.
-
Make 1px by 1px with a transparent background to avoid showing anything on the page.
-
Create a workflow, and add an action. Under the plugins tab, select the “Wait - Client Side” action. Alternatively, you can use the search bar to find this action.
3.5 Define how long you want to wait (in milliseconds)
-
Create a workflow with the “A Wait is done waiting” event.
-
Add whatever actions you want. These actions will only execute after the wait period is over.
Setup: Wait - Server Side🛠️
-
Create a workflow, then select the “Wait - Server Side” action.
-
Run some workflows right after, they will only run after the wait period has finished.
( Note using a server side wait will cause a progress bar to appear at the top of the browser window )
Editor
Demo
8 Likes
Thanks
The plugin is under review by the bubble team. It should be out soon!
1 Like
I also forgot to mention:
The sever side action returns true after the wait period is over.
And the client side action updates the exposed state to true when its wait period is over.
I’m not sure how useful that is, but it lets you trigger events elsewhere when the wait period is registered and complete.
Hope that helps 
1 Like
Also - Server Side waits are not replacements for recurring backend workflows. Any Server Side “wait” over 25 000 ms (25 seconds) will cause the action to timeout. However, you might be able to get away with it if you wait 25 seconds, and then run it " x " amount of time until your desired time (i.e 3,456 x 25 000 ms = 24 hours ). Haven’t tested it yet, but I’d be surprised if Bubble didn’t take any measure to prevent this.
1 Like
Last one
If you want multiple client side waits on a single page, and for them to do different things, you have to set id’s:
and then on the event …
1 Like
UPDATE
The plugin is out now. You can check it out here:
2 Likes
Hi @jonah.deleseleuc Jonah,
how much ressource it take when waiting? I will assume almost zero but it’s some kind of schedule or pause? 
1 Like
Almost 0! Just a set timeout
3 Likes
This is cool, i’ll be trying it out… i think it will help with some of my operations 
1 Like
Created this same thing for my own purposes recently!! Great minds think alike!
2 Likes
Thanks for the compliments!!
1 Like
Hi @jonah.deleseleuc
Do you know if the max wait is still 25 sec. and, maybe put this in the doc inside the plugin?
“if you wait 25 seconds, and then run it " x " amount of time until your desired time”
You mean put it one after the other or in loop sequence?
Hey!
Good idea, I’ll be sure to add that. Placing one “Wait” after another should actually work (like your screenshot shows), but I haven’t tested this. The 25 second is a limitation from Bubble unfortunately!
1 Like
Just tested this, I did three Server Side - Wait’s in a row (each 25 seconds long)
And it works 
1 Like
Great and thanks, I saved the time to test it 
. 
1 Like
No problem
I’m sure there’s a cap though, I doubt bubble would let that workflow run a thousand times.
Glad it worked though!
1 Like
Any sample use cases for this one?
1 Like
It’s flexible. Just like the default pause workflow action bubble has, sometimes you need to add a pause for whatever reason. The issue arises when you want to do that on the server side (backend workflows). This plug-in solves this
1 Like
