[BUG] Typebot Instagram connector Memory Leak Issue
Hey folks,
I’m hitting a pretty frustrating issue with Typebot when pulling in messages from Instagram, and I’m hoping someone here has run into this before or can point me in the right direction.
Here’s the setup: I’m using Typebot in combination with Chatwoot. First, I create an Instagram inbox on Chatwoot and then connect it with a Typebot agent bot. There’s a simple middleware in between that just parses the messages for Typebot to consume. The strange part is that whenever this agent bot is connected to an Instagram inbox, memory usage starts climbing and eventually the service crashes. But if I connect the same bot to any other inbox (like WhatsApp), everything runs fine — no leaks, no instability.
At first I thought it was just a resource issue, so I bumped up the limits. The extra capacity got eaten up just as quickly, which makes it clear this isn’t just about load, it’s a memory leak. We’ve tried multiple fixes, rolled back the Instagram connection to stabilize WhatsApp, and then re-added it a few times to be sure. The pattern repeats every time: stable without Instagram, unstable with Instagram.
What’s also confusing is that there are no error or warning logs on Chatwoot, Typebot, or my middleware when this happens — everything looks “normal” until the memory is gone. Everything is running on Kubernetes (EKS), with Chatwoot v4.5.2 and Typebot v3.4.2.
From what I can tell, something in the Instagram connector flow is leaking resources, but I can’t pin it down.
Has anyone else faced this with Instagram integrations in Typebot? Are there any known fixes, patches, or workarounds? Even advice on where to dig deeper for debugging memory behavior in this setup would be super helpful.
Thanks in advance — I’ve hit a wall on this one, and I’m sure others combining Chatwoot and Typebot for Instagram will eventually run into the same problem.
I’m hitting a pretty frustrating issue with Typebot when pulling in messages from Instagram, and I’m hoping someone here has run into this before or can point me in the right direction.
Here’s the setup: I’m using Typebot in combination with Chatwoot. First, I create an Instagram inbox on Chatwoot and then connect it with a Typebot agent bot. There’s a simple middleware in between that just parses the messages for Typebot to consume. The strange part is that whenever this agent bot is connected to an Instagram inbox, memory usage starts climbing and eventually the service crashes. But if I connect the same bot to any other inbox (like WhatsApp), everything runs fine — no leaks, no instability.
At first I thought it was just a resource issue, so I bumped up the limits. The extra capacity got eaten up just as quickly, which makes it clear this isn’t just about load, it’s a memory leak. We’ve tried multiple fixes, rolled back the Instagram connection to stabilize WhatsApp, and then re-added it a few times to be sure. The pattern repeats every time: stable without Instagram, unstable with Instagram.
What’s also confusing is that there are no error or warning logs on Chatwoot, Typebot, or my middleware when this happens — everything looks “normal” until the memory is gone. Everything is running on Kubernetes (EKS), with Chatwoot v4.5.2 and Typebot v3.4.2.
From what I can tell, something in the Instagram connector flow is leaking resources, but I can’t pin it down.
Has anyone else faced this with Instagram integrations in Typebot? Are there any known fixes, patches, or workarounds? Even advice on where to dig deeper for debugging memory behavior in this setup would be super helpful.
Thanks in advance — I’ve hit a wall on this one, and I’m sure others combining Chatwoot and Typebot for Instagram will eventually run into the same problem.
