Neon integration with Inngest exhausted my compute branch quota
Hello, I have some trouble while integrating Neon with Inngest.
I followed the Neon & Inngest tutorial to connect both platforms.
I first connected to my production branch (main) and observed that the events were correctly published.
Then I removed the integration on Inngest's side to connect with my develop branch instead (as it does not seem like we can manage several connections on Inngest's side).
Since then I'm totally stuck :
N.B: I might have misunderstood something as I am notan expert with Postgre WAL replication architecture.
I followed the Neon & Inngest tutorial to connect both platforms.
I first connected to my production branch (main) and observed that the events were correctly published.
Then I removed the integration on Inngest's side to connect with my develop branch instead (as it does not seem like we can manage several connections on Inngest's side).
Since then I'm totally stuck :
- My compute quota for develop branch went out of control (I am currently on the free pricing) : even after disconnecting on Inngest's side it appears that a connection is hold and is preventing the develop db to auto-shutdown after 5 mins. I can't find a way to remove the connection or manually shutdown the DB (without removing the branch).
- I tried several times to reconnect with my production database but I can't, I can go with all the integration wizard process but then it just does not work and if I come back to the integration view on Inngest, it continues to propose to "Connect" instead of the "Manage" button that should show that Inngest is properly connected with Neon.
N.B: I might have misunderstood something as I am notan expert with Postgre WAL replication architecture.
