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
I have revalidateOnReconnect turned on, but when user reconnects, fetch calls fire, but they all fail with error net::ERR_NAME_NOT_RESOLVED and thus showing error to user (cause api calls failed)
Is there a way to delay refetch after reconnect so this network error doesn't happen? or will I have to disable revalidateOnReconnect?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have revalidateOnReconnect turned on, but when user reconnects, fetch calls fire, but they all fail with error
net::ERR_NAME_NOT_RESOLVEDand thus showing error to user (cause api calls failed)Is there a way to delay refetch after reconnect so this network error doesn't happen? or will I have to disable revalidateOnReconnect?
Beta Was this translation helpful? Give feedback.
All reactions