Error message that does not disappear

Kurt · 2024-03-18T16:50:44.441Z

Operating system

Linux

Joplin version

2.14.19

Desktop version info

Joplin 2.14.19 (prod, linux)

Client-ID: f52269dae89743779390f7a0fb70da72
Sync-Version: 3
Profil-Version: 46
Unterstützter Schlüsselbund: Nein

Revision: 971c4e5

Backup: 1.4.0
Combine notes: 1.2.2
Csv Import: 1.0.1
Email Note: 1.2.2
Email Plugin: 1.0.0
Insert Date: 1.0.1
Note Variables: 2.0.0
Save Note as MD: 1.0.2
Templates: 2.4.0

Sync target

WebDAV

What issue do you have?

I get the error message every time I start Joplin
Einige Elemente können nicht synchronisiert werden. Zeige sie jetzt an
(see screenshot).
When I try to resynchronise the files, nothing changes. I created an "Ereignisprotokoll" (CSV) - is it useful? How can I send it to you?

Thanks for Your work and your efforts
Kurt

Screenshots

Bildschirmfoto_2024-03-18_17-39-15.png1913×158 28.3 KB

lucklh · 2024-04-07T15:56:45.629Z

I have the same issue. Don't know what to do.

Kurt · 2024-04-07T16:14:11.925Z

Finally, I "solved" the problem by searching for the problematic record (the internal number of the record is shown).
After finding the record -> delete it and restart Joplin.
Usually, this should work.

Regards

Kurt

(P.S.: I recommend to look if you can restore the content of your record before deleting it!)

personalizedrefriger · 2024-04-07T18:21:02.212Z

For future versions of Joplin, this pull request may be related:

github.com/laurent22/joplin

Mobile: Resolves #10245: Allow marking items as "ignored" in sync status

laurent22:dev ← personalizedrefrigerator:pr/mobile/allow-marking-sync-issues-as-ignored

opened 06:50PM - 03 Apr 24 UTC

personalizedrefrigerator

+292 -46

# Summary Adds an "ignore" button to the mobile sync status screen. Resolv…es #10245. # Notes - **At present, this "ignore" button is only shown on mobile.** On desktop, there are currently more options to resolve a sync issue (e.g. by deleting a large item through the attachments screen). - An "ignore" button is currently not shown for resource download failures. - This pull request adds a `sync_warning_dismissed` field to `sync_items`, which **requires upgrading the database**. - If an item has `sync_warning_dismissed = 1`, that item will not cause a "some items cannot be synchronized" warning to be shown (other items can still trigger the warning). - An item with `sync_warning_dismissed = 1` will still cause failures when attempting to switch sync targets. - **Note**: Particularly for errors like "exceeds maximum item size of 100 kB", it could make sense to still allow switching sync targets. - The sync status screen is migrated to TypeScript. # Screenshot ![screenshot: In addition to the existing "retry" buttons to the right of each item in the "sync failed" list, items have an "ignore" button](https://github.com/laurent22/joplin/assets/46334387/2e7237e4-39a1-4229-93cf-f1962ef21af9) # Testing Although this pull request has an automated test, it should also be tested manually. This can be done by: 1. Setting up Joplin Server sync. 2. Setting the maximum item size to a small number like 1024 (bytes) ![screenshot: Maximum item size set to 1024 in the Joplin Server config page](https://github.com/laurent22/joplin/assets/46334387/a670e13f-efce-4ccb-a022-cf5365a7812a) 3. Creating 1-2 items that are larger than this limit and syncing. 4. Clicking on the "some items could not be synchronized" banner. 5. Clicking "ignore" by each of the sync issue records. 6. Verifying that the "some items could not be synchronized" error message disappears. 7. Verifying that the item is moved under "ignored items" 8. Resyncing 9. Verifying that no sync warning is shown 10. Opening sync status (configuration > tools > sync status) 11. Clicking "retry" next to one of the ignored items 12. Resyncing 13. Verifying that the warning is shown again This has been tested successfully on an Android 12 emulator.

lucklh · 2024-04-08T11:41:18.994Z

Thanks a lot! Would be cool.

lucklh · 2024-04-08T11:44:30.320Z

Ups - sounds difficult. With which tool have you deleted the record? Have you directly modified database.sqlite in JoplinProfile?

Kurt · 2024-04-08T13:47:16.000Z

No, no, it's not difficult at all!
Just search for the "faulty" entry in Joplin itself and delete it. Unfortunately I didn't take a screenshot, but it's really quite simple. This was a spontaneous idea because I was terribly annoyed by this error message!
Joplin tells you in which entry the error is - that is then your search criterion!
Good luck!

Kurt

Wimvan · 2024-04-08T18:18:29.517Z

That confuses me. I receive the following error report and all I extract and search from the message will not be found. What would you search for? Thx in advance!

grafik2141×924 68.8 KB

Kurt · 2024-04-10T15:35:01.147Z

Unfortunately, I can't remember the exact procedure, but here is the important hint in your screenshot:

I was actually able to find the problematic entry (I think with the ID number) and then delete it.

Bildschirmfoto_2024-04-10_17-32-101355×120 10.4 KB

Good luck!

Kurt

system · 2024-05-10T15:35:28.902Z

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.