Recurring event properties
Events that trigger on the Bubble server at a specific interval.
This core reference entry is suited for advanced-level builders.
Learn more about experience levels.
To learn about this topic more in-depth, we recommend reading the suggested articles below:
Workflows
Recursive API workflows
An alternative way to set up recurring backend workflows is to use recursive workflows. These are not scheduled at a set interval, but are instead workflows that include an action that re-schedules the workflow when it's finished.
This method will consume more workload, but allows for dynamic recursion times.
Article: Recursive API workflows
The frontend and the backend
To learn more about the difference between frontend and backend workflows, we recommend the article below.
Article: The frontend and the backend
Debugging
All apps have the occasional bug, and our debugging tools help you squish them efficiently. The debugger helps you go through workflows step by step to see how they perform and the values they return.
Article series: Debugging your application
Bubble Academy: The Workflow Tab: Bubble Introduction Series [4/10] Bubble Academy: Understanding Workflow Execution Rules
Recurring event
Recurring events are defined in the backend workflow editor. Recurring events can be set to trigger at the following schedules:
None
Daily
Weekly
Monthly
Quarterly
Yearly
The schedule is set when the recurring event is first triggered by the Set/cancel a recurring event action. The interval is calculated that time onwards.
Properties
Recurring Event Name
Enter the name of the event. The name does not affect the workflow in any way.
Type of thing
A recurring event requires a thing to run on. Define the type here.
Ignore privacy rules when running the workflow
A recurring event runs in the context of the current user, so all relevant privacy rules are applied. In some cases, you may want the workflow to bypass these rules and run with admin-level permissions, with full access to data even without user authentication.
Check this box to bypass the privacy rules set in the Privacy section in the Data Tab.
Warning: Because these are security and privacy options, use this feature with caution.
Note: In very rare circumstances, it's possible for a recurring event to get in a bad infinite loop rescheduling itself. If this happens, you can pause the Scheduler, bulk delete all the extraneous scheduled tasks, unpause the Scheduler, and try again.
Timezone selection
Override the recurring event's timezone by setting an alternative timezone with a static or dynamic choice.
Timezone where event was scheduled
Uses the time zone reported from the browser of the user setting the event.
Static choice
Set a static time zone from a dropdown.
Time zone ID: sets the time zone ID you want to use.
Dynamic choice
Set a time zone from a dynamic expression.
Dynamic time zone: sets the time zone ID using a dynamic expression. Must match the IANA time zone format (also known as the tz database or Olson database format).
For this setting to be available you must first enable the setting Enable timezone override controls in your app's general settings.
Plan limits
Recurring events have limits on the number of recurring events per thing in the database. The limits are as follows:
Starter
1
Growth
5
Team
20
You can read more about our pricing plans on the page below.
Page: Bubble plans
Last updated
Was this helpful?