Suddenly the heartbeat does not reach the WebSocketListener an onUnhandledEvent method.
This happened several times a day in both the ap_northeast_1 and ca_central_1 regions.
Will this be improved by switching to the latest SDK? Currently, used version 134.
regards,
Hi Myoka,
This should not have anything to do with the SDK as we have not made any modifications to the SDK regarding the notification functionality. I would suggest you open a ticket with our customer care team with the date and time you failed to get heartbeats.
Remember that a failed heartbeat can also occur as a network issue within your data center hosting your code. I am not saying this is the case, but a customer care ticket would at least start the investigation process to see if anything happened.
Thanks,
John Carnell
Manager, Developer Engagement
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.