Hey everyone, need some help figuring out whatâs going on here.
Whatâs happening: The agenda page of my app started throwing this error on load for some clients:
Element AirCalendar Main_v2 - AAF Property contains circular reference to this element
Tried to update an autorun while it was already updating, cyclic
The error appears immediately on page load and keeps repeating every 2-3 seconds in the console.
What makes this weird:
- Works perfectly on the devâs machine
- Fails on the clientâs machine
- Cleared cache, incognito mode, updated Chrome â nothing fixes it
- Doesnât seem to be data-related (clearing localStorage didnât help either)
What worries me the most: Last Bubble update was ~7 days ago. The problem started today, but itâs spreading client by client in a cascade â some users still have normal access, but theyâre gradually losing it. This makes me think it might be something on Bubbleâs end (did the update break something in the plugin?) rather than a misconfiguration in my app.
Relevant stack:
- Bubble + AirCalendar Main_v2 plugin
- Data source via Supabase Realtime (WebSocket)
My suspicions:
- The last Bubble update introduced some change in the reactive system that broke compatibility with AirCalendar
- The plugin has a property
AAFthatâs somehow becoming self-referential - The Supabase Realtime connection might be triggering an update cycle in the element
Has anyone seen this kind of gradual cascade pattern before? Could it really be tied to the Bubble update? Any experience with AirCalendar behaving like this?