Kobo Sync - Book not found for entitlement ID

[Originalme]

What went wrong?

Originally one of our Kobo's was unable to download a book recently purchased from the Kobo store and it could not.

I ran a sync while tailing the logs and saw multiple Book not found for entitlement ID: XXX (XXX is ID's of books) warnings.

Looking for the the book ID's in Grimmory, they don't appear to exist anymore. So maybe they were books that were removed from the library.

How can we reproduce it?

I am not sure if this is 100% reproducible, as one of our Kobo's is working without throwing the errors on sync, but it also is not linked with a Kobo account with purchased DRM free eBooks.

Steps

It may be required to add a book to Grimmory, sync it to Kobo, and then delete it. I am going to run this test later today, or over the weekend on my working Kobo to see if that causes it.

1. Purchase a DRM Free eBook
   • Platform Decay is the one that started this (https://www.kobo.com/us/en/ebook/platform-decay)
2. Attempt to download the book from the kobo store directly on Kindle (no download option is available for this on ours)
3. Run a sync, and notice errors Book not found for entitlement ID: XXX

What Build of Grimmory are you on?

Stable

Your setup

• Grimmory Version: 3.03
• How are you running it: Debian 12 LXC on Proxmox host
• Browser: Firefox, Chromium, Kobo sync platform

Screenshots or error messages (optional)

Grimmory Log (journal) exported from LXC

• Full Log: grimmory.log

May 08 07:55:21 booklore java[3657]: 2026-05-08T07:55:21.493-07:00  WARN 3657 --- [booklore-api] [t-handler-11211] o.b.s.kobo.KoboReadingStateService       : Book not found for entitlement ID: 216
May 08 07:55:21 booklore java[3657]: 2026-05-08T07:55:21.555-07:00  WARN 3657 --- [booklore-api] [t-handler-11215] o.b.s.kobo.KoboReadingStateService       : Book not found for entitlement ID: 268
May 08 07:55:22 booklore java[3657]: 2026-05-08T07:55:22.308-07:00  INFO 3657 --- [booklore-api] [t-handler-11226] o.b.service.kobo.KoboEntitlementService  : Synced 5 tags to Kobo
May 08 07:55:22 booklore java[3657]: 2026-05-08T07:55:22.610-07:00  WARN 3657 --- [booklore-api] [t-handler-11228] o.b.s.kobo.KoboReadingStateService       : Book not found for entitlement ID: 216
May 08 07:55:22 booklore java[3657]: 2026-05-08T07:55:22.660-07:00  WARN 3657 --- [booklore-api] [t-handler-11234] o.b.s.kobo.KoboReadingStateService       : Book not found for entitlement ID: 268
May 08 07:55:59 booklore java[3657]: 2026-05-08T07:55:59.999-07:00  WARN 3657 --- [booklore-api] [t-handler-11278] o.b.s.kobo.KoboReadingStateService       : Book not found for entitlement ID: 216
May 08 07:56:00 booklore java[3657]: 2026-05-08T07:56:00.079-07:00  WARN 3657 --- [booklore-api] [t-handler-11283] o.b.s.kobo.KoboReadingStateService       : Book not found for entitlement ID: 268
May 08 07:56:00 booklore java[3657]: 2026-05-08T07:56:00.852-07:00  INFO 3657 --- [booklore-api] [t-handler-11296] o.b.service.kobo.KoboEntitlementService  : Synced 5 tags to Kobo
May 08 07:56:01 booklore java[3657]: 2026-05-08T07:56:01.108-07:00  WARN 3657 --- [booklore-api] [t-handler-11298] o.b.s.kobo.KoboReadingStateService       : Book not found for entitlement ID: 216
May 08 07:56:01 booklore java[3657]: 2026-05-08T07:56:01.183-07:00  WARN 3657 --- [booklore-api] [t-handler-11302] o.b.s.kobo.KoboReadingStateService       : Book not found for entitlement ID: 268

Before submitting

• I've searched existing discussions and this hasn't been reported yet
• I've reviewed this report and have completed it as fully as I can

[imnotjames]

This looks like a book was sync'd to the device and then deleted from your library so it no longer exists.

If you are able to grab the Kobo Sqlite database from .kobo/KoboReader.sqlite it may have information on what book has been deleted.

SELECT DISTINCT BookID, BookTitle FROM Content WHERE BookID IN ('216', '218')

[Originalme]

That's the table I was looking at that we discussed in Discord. No hits there.

[imnotjames]

Is there a file 216 & file 218 under .kobo/kepub directory?

[Originalme]

This may actually be related to https://github.com/orgs/grimmory-tools/discussions/1216

[imnotjames]

Possible but unlikely. These are two fairly different areas.