Recurring event

Events that trigger on the Bubble server at a specific interval.

This core reference entry is suited for advanced-level builders.

Recurring event

Recurring events are defined in the . Recurring events can be set to trigger at the following schedules:

  • None

  • Daily

  • Weekly

  • Monthly

  • Quarterly

  • Yearly

Note that 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.

Event name

Enter the name of the . The name does not affect the workflow in any way.

Type of thing

A recurring event requires a to run on. Define the type here.

Ignore privacy rules when running the workflow

A recurring is run . All apply accordingly. Sometimes you want the workflow to bypass these rules and be run as an admin user who has all rights on the data, even when run without 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.

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 in the database. The limits are as follows:

Plan
Recurring events per thing

Starter

1

Growth

5

Team

20

You can read more about our pricing plans on the page below.

Page: Bubble plans

Last updated

#829: Flusk: more detailed Issue Descriptions

Change request updated