TanStack•7mo ago•

10 replies

propagating errors to global error boundary

I am running a queryClient.fetchQuery inside of an onChange validator... when it throws a server error, I want it to use my global error boundary, but I'm noticing that it's getting swallowed and is just getting set to the localized error object, is there a way around this?

TanStack is a community of passionate software engineers striving for high-quality, open-source software for web devs

28,257Members

View on Discord

Resources

Recent Announcements

Similar Threads

Was this page helpful?

Product

Pricing Docs Communities

Resources

About Blog Changelog Contributors

Legal

Terms Privacy Cookies EULA

Twitter GitHub Discord

© 2026 Hedgehog Software, LLC. All rights reserved.

© 2026 Hedgehog Software, LLC

Twitter GitHub Discord

More

Communities Docs About Terms Privacy

Recent Announcements

dry-scarlet

https://x.com/powersync_/status/2010721010006552775?s=20

dry-scarlet · 4h ago

dry-scarlet

You can now submit your website/app/project to http://TanStack.com 's new showcase and have it seen by the TanStack community! - Global showcase browser - Per-library filters - Category filters Submit here: https://tanstack.com/showcase/submit View all here: https://tanstack.com/showcase

dry-scarlet · 2w ago

dry-scarlet

TanStack AI Alpha 2 is here! 🖼️ Image, video, audio, speech, transcription, structured output 📦 Split adapters = smaller bundles, faster dev/contributions, easier 🎄 Fully tree shakable adapters ✨ Cleaner, flattened, fully type-safe APIs https://tanstack.com/blog/tanstack-ai-alpha-2

dry-scarlet · 4w ago

Similar Threads

Error propagating to parent routes

TTanStack / router-questions

reset error boundary if query succeeded

TTanStack / react-query-questions

useParams is not propagating

TTanStack / start-questions

Global error handling & Localization

TTanStack / react-query-questions