Course contentsShow
← React
Lesson 1324 of 2,39633. Error BoundariesFree lesson

The resetErrorBoundary Function

How to programmatically reset error state and re-render the component tree after an error.

The resetErrorBoundary Function

What you'll learn: How the resetErrorBoundary function from react-error-boundary lets you programmatically recover from errors and re-render your component tree.


When an error boundary catches an error, it displays your fallback UI—but users need a way to recover from that error state. The resetErrorBoundary function is the escape hatch that clears the error and attempts to re-render the component tree that failed.

How It Works

When you provide a FallbackComponent to <ErrorBoundary>, that component automatically receives resetErrorBoundary as a prop. Calling this function does two things:

  1. Clears the error state inside the boundary
  2. Re-mounts the component tree, giving it a fresh attempt to render

Think of it like hitting the "try again" button after a failed operation—you're telling React, "Okay, the problem might be fixed now, let's attempt this again from scratch."

Typical Usage Pattern

Your fallback component receives resetErrorBoundary and typically wires it to a button:

function ErrorFallback({ error, resetErrorBoundary }) {
  return (
    <div role="alert">
      <p>Something went wrong:</p>
      <pre>{error.message}</pre>
      <button onClick={resetErrorBoundary}>
        Try again
      </button>
    </div>
  );
}

When the user clicks "Try again," React clears the error and re-renders the children. If the underlying problem was transient (like a network hiccup), the component might succeed this time.

When the Reset Happens

The reset is immediate—React doesn't wait or retry automatically. If the same error occurs again, you'll just land back in the error state. This is why resets often work best when combined with state changes that might fix the root cause.

Key Takeaway: resetErrorBoundary gives users a way to recover from errors by clearing the error state and re-mounting the failed component tree—essential for creating resilient UIs.