Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Synchronization behavior #11578

Open
Pilat66 opened this issue Jan 4, 2025 · 1 comment
Open

Invalid Synchronization behavior #11578

Pilat66 opened this issue Jan 4, 2025 · 1 comment
Labels
bug It's a bug

Comments

@Pilat66
Copy link

Pilat66 commented Jan 4, 2025

Operating system

Linux

Joplin version

3.0.15

Desktop version info

Joplin 3.0.15 (prod , linux)

Current behaviour

  1. Start Joplin
  2. Synchronization started
  3. Press "Cancel" button
  4. Synchronization dont stop, removing all elements continues

Expected behaviour

  1. Start Joplin
  2. Synchronization started
  3. Press "Cancel" button
  4. Synchronization STOP, deletion of all elements is cancelled or at least synchronization is stopped

Logs

Deleted remote items: 1077.
Completed: 2025-01-05 01:32 (3894s)
Last error: Sync target is locked - aborting API call

@Pilat66 Pilat66 added the bug It's a bug label Jan 4, 2025
@mrjo118
Copy link
Contributor

mrjo118 commented Jan 6, 2025

Unfortunately when cancelling the sync, it can only be interrupted at certain stages as far as I'm aware, so it is normal for cancelling to continue some actions before it stops.

However, you were likely prompted to cancel the sync due to seeing many deletions, which is likely due to note history cleaning now working correctly in newer versions of Joplin (it did not work correctly for a long time). See #11488 for more information regarding this.

On Joplin desktop, go to Tools > Export deletion log. Here you can confirm what items were deleted in your sync yesterday, if they were in fact majority or entirely revisions. There is an equivalent log which can be viewed on the mobile app as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug It's a bug
Projects
None yet
Development

No branches or pull requests

2 participants