How to determine the cause of "RealtimeSet received delta update for non-existent key"
Recently we've been getting tons of error logs for "RealtimeSet received delta update for non-existent key". I assume this is because multiple clients are writing to the same object in a room that was destroyed, but is there an easier way to determine which object is causing the error?
3 Replies
Hi @fojam. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hmm, I don't know enough to give you a confident answer yet. The knowledge sources provided do not contain specific information about the error "RealtimeSet received delta update for non-existent key". However, it's worth noting that similar issues can occur when multiple clients attempt to delete the same model from a RealtimeSet at the same time.
To prevent this, it's generally recommended to have the client that owns the object destroy it. Here's a code snippet that might help:
This code checks if the object is owned locally before attempting to destroy it, which can help prevent conflicts if multiple clients are trying to delete the same object simultaneously.
For more detailed troubleshooting, you might want to refer to the official Normcore documentation (https://normcore.io/documentation/).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
<@119985475967516673> kapa.ai is still learning and improving, please let us know how it did by reacting below
Nothing at the moment unfortunately. We've got an issue written up to add more verbose logs.