Skip to content

Question about client sync key #137

Answered by bgregos
bradyt asked this question in Q&A
Mar 2, 2022 · 3 comments · 5 replies
Discussion options

You must be logged in to vote

To answer your initial question:

While I don't have a taskserver set up right now to test with, here's what's happening on Foreground's side:

  1. You send task "bar" to the messed up taskserver.
  2. The taskserver responds "Client sync key not found". This string is coming from the server, Foreground doesn't contain that text.
  3. On sync failure, Foreground keeps the sync key and list of changed tasks in place in case a later sync succeeds.
  4. Disable sync. This doesn't send anything to the server, but it purges the key from Foreground.
  5. You re-enable sync. Foreground sends a statistics message to the server to ensure that it's up and that the configuration is correct. No task data is sent here, nor is…

Replies: 3 comments 5 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@bradyt
Comment options

Answer selected by bradyt
Comment options

You must be logged in to vote
4 replies
@bradyt
Comment options

@bradyt
Comment options

@bradyt
Comment options

@bradyt
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
2 participants