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
There are no retry mechanisms for sending any message content to the server.
The reason for this is because if something does go wrong when data is being sent - it carries low severity, hence the user is free to retry again and they are fully aware that there is some sort of a problem with the backend.
You can also observer that ChatGPT (to-date) also does not have a retry mechanism - potentially due to the same reason.
May I ask, what motivated you to raise this issue? Thanks!
There are no retry mechanisms for sending any message content to the server.
The reason for this is because if something does go wrong when data is being sent - it carries low severity, hence the user is free to retry again and they are fully aware that there is some sort of a problem with the backend.
You can also observer that ChatGPT (to-date) also does not have a retry mechanism - potentially due to the same reason.
May I ask, what motivated you to raise this issue? Thanks!
hi @OvidijusParsiunas
When I start recording with the microphone and send it to a custom backend service via DeepChat, if a network error occurs during the JS XHR request, the recording just made becomes invalid, and I need to record again.
Ok, that seems to be quite serious.
I am currently working on another feature right now, but I will try to find a way to retain the recordings as soon as I get time.
I will update you when I have come up with a fix.
If I upload a voice file to the backend service and the upload is interrupted due to network issues, is there a retry mechanism in place?
The text was updated successfully, but these errors were encountered: