Richer usePaginatedQuery

[salemkode]

I am looking for richer use of PaginatedQuery.
Since the convex-tanstack plugin does not support infinite scroll, we will need to have more status about pagination.

( We do not want the app to crash just for errors in the server. )

[ianmacartney]

I'm hearing that the error is the big ask here, since pagination already has status, is that right?

[ianmacartney]

And you don't care which page the error is for I'm guessing? If all pages error (e.g. on auth error), does it make sense to return an array or the "first" one?

[salemkode]

When a user logs out, I want to make sure my app never crashes due to unhandled errors.
Currently, usePaginatedQuery’s status only reports pagination state (like loading more or has more to load), but it doesn’t provide any information about query errors.

From what I can tell, status is not designed to handle errors—it only tracks loading/pagination—and any thrown error from the query will bubble up and potentially crash the app if not caught externally.

Is there a recommended way to handle errors for usePaginatedQuery without wrapping the entire component in a React error boundary?

[ianmacartney]

Is this component inside of an `<Authenticated>` tag? When the user logs out, are you redirecting them to another page at the same time?

…

On Fri, Aug 1, 2025 at 7:39 PM Salem Mohammed Shamakh < ***@***.***> wrote: *salemkode* left a comment (get-convex/convex-helpers#705) <#705 (comment)> When a user logs out, I want to make sure my app never crashes due to unhandled errors. Currently, usePaginatedQuery’s status only reports pagination state (like loading more or has more to load), but it doesn’t provide any information about query errors. From what I can tell, status is not designed to handle errors—it only tracks loading/pagination—and any thrown error from the query will bubble up and potentially crash the app if not caught externally. Is there a recommended way to handle errors for usePaginatedQuery without wrapping the entire component in a React error boundary? — Reply to this email directly, view it on GitHub <#705 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACZQW4P2KYNQQZIKP6KG4T3LQQHXAVCNFSM6AAAAACCSWA6XOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNBWGE2TAMRTGU> . You are receiving this because you commented.Message ID: ***@***.***>