This message was deleted.
# cloud
s
This message was deleted.
a
what version of the server sdk package are you on?
(thanks for flagging this)
e
1.1.0
d
are you seeing this fail consistently? or is it sporadic? currently certain some requests are getting a 500 returned erroneously even when the operation has succeeded. This is due to a short timeout set on our APIs and the fact that it can take longer to fulfill these requests at times.
e
Seems sporadic, but I need to debug more
d
your deletion should have gone through still. for now I think it's ok to ignore the errors here. we will be making improvements to the API layer soon.
e
okay
Are there other API calls that could be failing?
Is this issue affecting the whole API or just delete?
FYI... testing deleting and in some cases I get the 500 and the room is not deleted.
or potentially it fails but can then take a long (very long) time to complete
d
can you give me a room name that had failed? will pull some logs to double check
e
I'll dig one out
Will rooms always have the possibility to take some time to delete?
Or along with the 500 is this unexpected?
We started to handle deleting rooms due to the fact the "room end" event wasn't triggering
Which I believe is a known bug based on a previous conversation we had.
Just want to understand the situation as it may require us to refactor a bit.
d
Room can take a bit of time to delete. We've made them more consistent in the last few weeks but there's probably more work to do. Digging into examples of when it didn't' work would be helpful. No worries if you can't find it. We are actually deploying a change today that will end rooms much more quickly after they are done. so by your morning it should be working a lot better
e
okay thanks
we are getting the room finished events now
🙌 1
so I have adjusted for that