Collections sometimes get "stuck"
I apologize in advance for this pretty vague-sounding question. First off I've read the docs section on error handling but I'm not sure they apply here.
When I observe the network tab in the console I can see the effect of the window gaining visibility because my collection(s) connection(s) ends with
I feel like I must have set something up wrong somewhere, but I'm not sure what. I'm using the Electric SQL API proxy approach as described in the docs.
What is the expected long-running behavior of a collection (in this case Electric SQL)? Should it "time out" like this and/or should it automatically reconnect if it does?
When I observe the network tab in the console I can see the effect of the window gaining visibility because my collection(s) connection(s) ends with
NS_BINDING_ABORTED and a new one starts. It seems that when this happens enough times, or I leave the tab for long enough (not sure which), this stops and my collection becomes stuck. I can no longer see new connections being made in the network tab. Doing something on the site (like sending a new message, which should be returned by a messages collection) confirms this - it doesn't show up until I refresh. I feel like I must have set something up wrong somewhere, but I'm not sure what. I'm using the Electric SQL API proxy approach as described in the docs.
What is the expected long-running behavior of a collection (in this case Electric SQL)? Should it "time out" like this and/or should it automatically reconnect if it does?
