If I use the onError mutateoptions why cant I rethrow error and make notification provider catch it?
If I use the onError in mutateoptions why cant I rethrow error and make notification provider catch it?
KHi @Todilo. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. 
K----------------------
The issue you're encountering relates to how error handling works in refine's data hooks and the notification system. Based on the knowledge sources, there are a few key points that explain why rethrowing errors in
When you use
As shown in the refine architecture code:
Instead of trying to rethrow errors, you have several better options:
The issue you're encountering relates to how error handling works in refine's data hooks and the notification system. Based on the knowledge sources, there are a few key points that explain why rethrowing errors in
onErrorWhy rethrowing doesn't work
When you use
onError- The data hook (e.g., ) catches the error from the API call
- It automatically processes this error, including sending it to the notification provider
- Then it calls your custom
handleronError
onErrorAs shown in the refine architecture code:
Better approaches for custom error handling
Instead of trying to rethrow errors, you have several better options:
- Use the property
KMany refine hooks like , , and
This approach is recommended in the useUpdate documentation.
For custom event handlers where you need more control, you can use the
If you're working with forms and want to display server errors in the form itself (not just notifications), you might need to manually handle this using the callback, as discussed in this GitHub issue.
It's also worth noting that React's error boundaries (which might be part of your error handling strategy) have limitations and don't catch errors in event handlers or asynchronous code, as mentioned in the Error Boundaries in React blog post.
useFormThis approach is recommended in the useUpdate documentation.
- Use try-catch with useNotification
For custom event handlers where you need more control, you can use the
useNotification- For form errors specifically
If you're working with forms and want to display server errors in the form itself (not just notifications), you might need to manually handle this using the callback, as discussed in this GitHub issue.
Error boundary limitations
It's also worth noting that React's error boundaries (which might be part of your error handling strategy) have limitations and don't catch errors in event handlers or asynchronous code, as mentioned in the Error Boundaries in React blog post.
KFor the most robust error handling, consider using a combination of refine's built-in error notification system and custom error handling for specific cases.
----------------------
Note: you can ask me a follow up question by @ mentioning me again
----------------------
----------------------
Note: you can ask me a follow up question by @ mentioning me again
----------------------
K@207945811592478720 Kapa.ai is still learning and improving, please let me know how I did by reacting below.
S@kapa.ai not sure what I am doing wrong but if I use the onError callback in mutationoptions I no longer get the notification, the useupdate onerror seem to no longer be called
KLet me check the knowledge base for you again. One moment! 
K----------------------
You're encountering a known behavior in refine's data hooks. When you provide your own
This is documented in several places in the refine codebase. For example, in the documentation:
useDelete documentation
The same applies to and other data hooks. When you provide your own error handler, refine assumes you want to take complete control of error handling.
Instead of using
useUpdate errorNotification documentation
If you need to use
```javascript
import { useNotification } from "@refinedev/core";
// In your component
const { open } = useNotification();
You're encountering a known behavior in refine's data hooks. When you provide your own
onErrorThis is documented in several places in the refine codebase. For example, in the documentation:
useDelete documentation
The same applies to and other data hooks. When you provide your own error handler, refine assumes you want to take complete control of error handling.
Solutions:
- Use the property instead
Instead of using
onErroruseUpdate errorNotification documentation
- Call the notification manually in your onError handler
If you need to use
onError```javascript
import { useNotification } from "@refinedev/core";
// In your component
const { open } = useNotification();
Kconst { mutate } = useUpdate({
mutationOptions: {
onError: (error, variables, context) => {
// Your custom error handling logic
// Manually trigger notification
open({
message: ,
description: error.message,
type: "error"
});
}
}
});
errorNotification` property when you want to customize notifications while preserving refine's error handling flow.
----------------------
Note: you can ask me a follow up question by @ mentioning me again
----------------------
mutationOptions: {
onError: (error, variables, context) => {
// Your custom error handling logic
// Manually trigger notification
open({
message: ,
description: error.message,
type: "error"
});
}
}
});
errorNotification` property when you want to customize notifications while preserving refine's error handling flow.
----------------------
Note: you can ask me a follow up question by @ mentioning me again
----------------------
K@207945811592478720 Kapa.ai is still learning and improving, please let me know how I did by reacting below.
SFor anyone who might wander here the github issue https://github.com/refinedev/refine/issues/5888 solved my problem. When calling the mutate I change to mutateAsync . I wanted to redirect and/or re-enable my form buttons after mutate and I used mutateAsync(...).finally(() => { cleanup here, or redirect })
GitHub
Describe the bug Consider this: import { useLogin } from "@refinedev/core"; const { mutateAsync: login, isLoading } = useLogin({ mutationOptions: { onSuccess(data) { console.log("Hey...