I’ve implemented a standard React Error Boundary and even tried wrapping it with a client-side retry mechanism — changing a key, hiding/showing the component, using router.refresh(), etc. None of these actually cause the Server Component to remount or re-render its children after an error has occurred.

I know that Next.js provides the error.tsx file at the route level, but that’s not what I want here. My component needs to manage its own error handling, since it will be reused across multiple pages, not just a single route.

How can I properly recover or re-render a Server Component (not a Client Component) after it has thrown an error, without using a route-level error.tsx boundary?

Is there any pattern or API in Next.js that allows retrying or remounting a failed Server Component from a client-side boundary?