You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our system is capturing from time to time, once a month more or less, the following error that seems that is not handled by the SDK.
Error: connect ETIMEDOUT 34.96.125.79:443
at __node_internal_captureLargerStackTrace (node:internal/errors:477:5)
at __node_internal_exceptionWithHostPort (node:internal/errors:655:12)
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1247:16)
That IP address is the IP address of mixpanel eu API as can be seen in the DNS records for api-eu.mixpanel.com.
In our code we are promisifying mixpanel.track and capturing the errors sent to the callback, however, fmpov this should have been handled by the SDK and been retried by the SDK.
At the end, has that event been sent, we guess that isn't sent.
Is this the expected behaviour?
Does the SDK handle any error by itself?-
Should all errors be handled by the integrator?
What other errors can be thrown by the SDK?
The text was updated successfully, but these errors were encountered:
Our system is capturing from time to time, once a month more or less, the following error that seems that is not handled by the SDK.
That IP address is the IP address of mixpanel eu API as can be seen in the DNS records for api-eu.mixpanel.com.
In our code we are promisifying
mixpanel.track
and capturing the errors sent to the callback, however, fmpov this should have been handled by the SDK and been retried by the SDK.At the end, has that event been sent, we guess that isn't sent.
The text was updated successfully, but these errors were encountered: