You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To ensure efficient investigation of the issue, please fill out the fields below with as much detail as possible. Reports that do not follow this template may be closed without notification. We appreciate your cooperation.
Describe the bug
The WebSocket connection delivers chunks very slowly until it fails sending at all. Depending on where in the process the connection failed, you can refresh the page most of the time and the GET request will retrieve the full conversation correctly. I have already increased the RAM settings on the websocket handler lambda, but it does not seem too improve the situation.
To Reproduce
Steps to reproduce the behavior:
Run any larger conversation
wait for the failure to happen
Refresh the page
See that the convo is complete, even though the connection broke before
The text was updated successfully, but these errors were encountered:
🚨 Please Note 🚨
To ensure efficient investigation of the issue, please fill out the fields below with as much detail as possible. Reports that do not follow this template may be closed without notification. We appreciate your cooperation.
Describe the bug
The WebSocket connection delivers chunks very slowly until it fails sending at all. Depending on where in the process the connection failed, you can refresh the page most of the time and the GET request will retrieve the full conversation correctly. I have already increased the RAM settings on the websocket handler lambda, but it does not seem too improve the situation.
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: