Invalid Synchronization behavior

[Pilat66]

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

[mrjo118]

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

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[Pilat66]

Hi!

The issue is not fixed and probably cannot be fixed due to architectural flaws in Jopplin. There are several synchronization-related issues, ranging from inconsistency to very poor performance.
The topic can be closed.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.