woven cliff
Hi team,
I am facing the issue of preview environment is closing the web socket connection after 60 seconds, upon searching a bit it looks like emergent is stopping after 69 seconds in the preview environment.
Here is the job id: 44144550-a7b1-430a-b1ff-ec846685ee15
I also sent an email 3 hours ago but didn’t heard back yet.
Can you help me troubleshooting this issue? This is fix as I need to push changes onto production app.
woven cliff
@livid elk would you mind checking internally?
woven cliff
<@&1446187512253911261> <@&1404346284122308690> <@&1325936972023201885> @thorn sigil @granite needle
granite needle
Hey could you please make a ticket at [email protected] thats something we as guides cant handle
woven cliff
I do raised the ticket and it’s been 18 hours at this stage and haven’t received any response really need to resolve this
thorn sigil
Hey could you please make a ticket at [email protected] thats something we as ...
It's a known bug I have this happen all the time it's instant for me right after typing a new prompt it locks the chat session you can't type. the workaround is pinned in general @granite needle if you refer to that pinned post for future tickets I created it last year when I noticed it was happening.
slate ermine
Same issue i am also facing it autorefresh preview mode after every 1 minute.
woven cliff
It's a known bug I have this happen all the time it's instant for me right after...
Deploying the changes into production environment would it impact the existing app ?
woven cliff
It's a known bug I have this happen all the time it's instant for me right after...
Also, not able to find your pinned about for the workaround
woven cliff
It's a known bug I have this happen all the time it's instant for me right after...
"Thanks for the reply, but my issue is actually different from the chat session locking bug mentioned.
I am facing a Backend Infrastructure Timeout specifically affecting WebSockets in the Preview environment. Here are the technical details:
The Symptom: Every WebSocket connection (Twilio <-> Deepgram Bridge) is being hard-terminated at exactly 60 seconds.
The Error: Twilio reports Error 31921 (Connection reset without closing handshake).
What I’ve already tried: I have implemented application-level JSON heartbeats ('marks') and injected binary silence frames every 10 seconds to keep the connection active. These are being ignored by the gateway.
The Diagnosis: This looks like a hard-coded proxy_read_timeout or idle_timeout on the Preview Load Balancer/Ingress Controller.
Is this 60-second limit a hard constraint of the Preview Tier? If so, will moving this to a Production Deployment on Emergent remove this specific gateway timeout?"