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
Retries after timeout errors immediately run into timeout after 0 ms
It looks like the SDK is reusing the AbortController from the initial request. But this is already timed out and will no longer work. Possible solution: Create a new AbortController for every request/retry
Here is a screenshot from our logs when the issue happens: The logging is done by wrapper around the fetch function. NETWORK_ERROR means there was no HTTP response status code
Retries after timeout errors immediately run into timeout after 0 ms
It looks like the SDK is reusing the AbortController from the initial request. But this is already timed out and will no longer work. Possible solution: Create a new AbortController for every request/retry
Here is a screenshot from our logs when the issue happens: The logging is done by wrapper around the fetch function. NETWORK_ERROR means there was no HTTP response status code
here the init of the client
The text was updated successfully, but these errors were encountered: