Engineering have identified a race condition in very rare circumstances and it’s currently being addressed. It should be pushed out pretty soon.
Great - it is needed. Loosing web hook response has also been seen happening on a device with 1.5.2 today. So we are out of options, as OS versions before 1.5.2 makes little sense with B523.
The fix is live and if your device reconnects it should be pointed to the primary server.
(Power cycle is best)
If you don’t clear the session manually it will expire once the 72hr timer runs out.
1 Like
Thanks 
(I currently clear the session at every startup from device side).
Confirmed to be working for days now on B523, so we continue to get upload confirmation back from our servers before deleting uploads
1 Like
hmm … new problem introduced instead. When the webhook can not find the recipient internet address, the webhook sends OK web response back to the device that dumps the upload and data are lost.
Previously an unfound webhook address would provide a webhook error response, and data was saved until a confirm was received from our servers at a later attempt …
Can I ask that you please submit a ticket with details on the account, device and relevant webhook so that we can look at the logs?
Pulled the trigger too fast on this one. The problem was with one of the used libraries.
1 Like
This topic was automatically closed after 44 days. New replies are no longer allowed.