We recently exceeded our account quota, which caused the convo functionality to stop working but our client code never received an error from this framework. When this happened I see the following error printed in the console:
❌ [Conversation] Failed to parse incoming event: invalidEventData
❌ [Conversation] Raw data: {"type": "error", "message": "received 1002 (protocol error) This request exceeds your quota limit.; then sent 1002 (protocol error) This request exceeds your quota limit."}
Looking at the code for these lines you can see these error are just swallowed here and never reported via the various callbacks from ConversationConfig.
We recently exceeded our account quota, which caused the convo functionality to stop working but our client code never received an error from this framework. When this happened I see the following error printed in the console:
❌ [Conversation] Failed to parse incoming event: invalidEventData
❌ [Conversation] Raw data: {"type": "error", "message": "received 1002 (protocol error) This request exceeds your quota limit.; then sent 1002 (protocol error) This request exceeds your quota limit."}
Looking at the code for these lines you can see these error are just swallowed here and never reported via the various callbacks from ConversationConfig.