Skip to content
Discussion options

You must be logged in to vote

There are a couple of states that useLiveQuery provides, one is persisting. Use that to show some type of UI to the user that the data hasn't been synced yet before they leave the page.

https://tanstack.com/db/latest/docs/guides/error-handling#transaction-states-and-error-information

If they leave and the mutation fails and they log back in, there wouldn't be a way for useLiveQuery to resume because it's in-memory, the failed sync won't show up.

It sounds like you want a different solution to this, something like redis that can temporarily store the request and status that can be separately checked and can retry on its own without the user being signed in, or atleast can show a user that …

Replies: 1 comment 6 replies

Comment options

You must be logged in to vote
6 replies
@FatahChan
Comment options

@Asjas
Comment options

@FatahChan
Comment options

@Asjas
Comment options

Answer selected by FatahChan
@Asjas
Comment options

@FatahChan
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants