Can someone tell me if the AirCalendar is constantly searching for updates in the database? With bubbles new Work Unit pricing model, I am digging into what is using up my work units. Searches for an object we call bSessions is using almost 90% of my work units. bSessions are the object we display on 6 airCalendar elements.
How can i reduce the searches the airCalendars are performing so that I am not using so many WU’s?
I have been working with Bubble support. The AirCalendar does chew thru a lot of Work Units (WUs) when you use a search in the Events Data Source field The reason is that it continually checks on the server side for updates. To fix this I changed my Events Data Source field to pull from a custom state (list) and then use workflows to keep the custom state updated when things change. Now as I check the logs in Bubble I see a 88% reduction in the WUs I am using.
Hello, @ianhayes2121. Thank you for your question and your patience. 
Yes, except for the Bubble, which is constantly checking the database changes, the plugin is also requesting the database to keep the plugin element updated with the events created/removed inside the Appointment data tab. That happens only within the active session when the user interacts with the calendar.
Hope it helps! Let me know if you have any questions.
Have a good Friday. 
so for apps built around the calendar, that session can be remain active for many users ALL DAY. This will use up many WUs and end up being very expensive.
For anyone where this is their use case, I highly recommend you make the changes I describe above.
Yup, putting the Air Calendar’s element data source into the custom state can do a trick because a bit different mechanism is used to update its content.
Please let me know if you have any questions about the plugin.
