Replies: 1 comment
-
we don’t expose retry failures, retries are pretty much an opaque process. but retry can be a function so you can hook into that if you want. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
I'm using
useMutation
in my application and I have configured it withretry: true
andretryDelay: 10_000
. My expectation is that the mutation will retry every 10 seconds after a failure.However, I'm having trouble identifying when exactly the retry happens. Once the mutation starts, its status becomes Pending and stays that way throughout the retries. This makes it unclear whether the retry logic is actively attempting the operation again or simply waiting for the retry delay to elapse.
Is there any way to observe or be notified about the retry attempts? For example, is there a method or state in useMutation that provides insight into when a retry is happening, or should I implement some custom logic to track this?
Any help or suggestions would be greatly appreciated!
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions