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
Describe the Bug
When making a rest call to /chats/<chat-id>/events for a chat that does not exist, a request timeout occurs. This is because the request goes to a ChatActor which is a sharded actor. This actor boots up and immediately determines that the chat does not exist and shuts down. It does this without responding to the incoming request.
Expected Behavior
There should still be a response back to the chat rest actor so a "not_found" HTTP response can be given.
The text was updated successfully, but these errors were encountered:
Versions
Describe the Bug
When making a rest call to
/chats/<chat-id>/events
for a chat that does not exist, a request timeout occurs. This is because the request goes to a ChatActor which is a sharded actor. This actor boots up and immediately determines that the chat does not exist and shuts down. It does this without responding to the incoming request.Expected Behavior
There should still be a response back to the chat rest actor so a "not_found" HTTP response can be given.
The text was updated successfully, but these errors were encountered: