Sync on Save can run multiple consequtive syncs after file saves. As mentioned briefly in a comment in #88.
I believe this is because it schedules a sync even though one is ongoing or one is already scheduled and hasn't ran yet. This piles up multiple syncs even though it just needs one.
Could be better to check if a sync is ongoing and queue a sync once it is finished. Additionally it should check if a sync is already scheduled and hasn't ran yet before scheduling another sync. Unless this is the intended behaviour of being able to queue a sync in x amount of time?
I'm happy to have a look into this.
What OS are you using?
Windows, Android
What remote cloud services are you using?
Dropbox
Version of the plugin
No response
Version of Obsidian
No response
Using password or not
[X] Yes.
Ensure no sensitive information
[X] I ensure that no sensitive information is submitted in the issue.
What happened?
Sync on Save can run multiple consequtive syncs after file saves. As mentioned briefly in a comment in #88.
I believe this is because it schedules a sync even though one is ongoing or one is already scheduled and hasn't ran yet. This piles up multiple syncs even though it just needs one.
Could be better to check if a sync is ongoing and queue a sync once it is finished. Additionally it should check if a sync is already scheduled and hasn't ran yet before scheduling another sync. Unless this is the intended behaviour of being able to queue a sync in x amount of time?
I'm happy to have a look into this.
What OS are you using?
Windows, Android
What remote cloud services are you using?
Dropbox
Version of the plugin
No response
Version of Obsidian
No response
Using password or not
Ensure no sensitive information