[DaySleeper]

KeyError: error synchronizing data

calibre, version 6.14.1
ERROR: Unhandled exception: <b>KeyError</b>: Error synchronizing data

calibre 6.14.1 Portable embedded-python: True
Windows-10-10.0.19045-SP0 Windows ('64bit', 'WindowsPE')
('Windows', '10', '10.0.19045')
Python 3.10.1
Windows: ('10', '10.0.19045', 'SP0', 'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins: DeACSM (0, 0, 16) && Gather KFX-ZIP (from KFX Input) (2, 6, 0) && DeDRM (10, 0, 3) && Package KFX (from KFX Input) (2, 6, 0) && Access Aide (0, 1, 13) && Action Chains (1, 18, 19) && Annotations (1, 17, 13) && Calibre Power Search Plugin (2, 2, 0) && CalibreSpy (1, 0, 92) && Count Pages (1, 12, 1) && DOC Input (1, 0, 1) && Ebook Translator (2, 0, 3) && Editor Chains (0, 8, 3) && EpubMerge (2, 17, 0) && EpubSplit (3, 6, 0) && FanFicFare (4, 20, 0) && FictionDB (1, 4, 1) && Find Duplicates (1, 10, 7) && GetFileName (0, 2, 0) && Goodreads (1, 7, 3) && Goodreads_Rating (4, 0, 0) && Job Spy (1, 0, 205) && KFX metadata reader (from KFX Input) (2, 6, 0) && KFX Input (2, 6, 0) && Set KFX metadata (from KFX Output) (2, 3, 1) && KFX Output (2, 3, 1) && Kindle Collections (1, 7, 29) && KindleUnpack - The Plugin (0, 83, 1) && Mass Search-Replace (1, 7, 1) && Media File Importer (1, 0, 27) && Modify ePub (1, 8, 2) && Open With (1, 8, 1) && OverDrive Libby (0, 1, 9) && Overdrive Link (2, 57, 0) && Reading List (1, 15, 1) && Save To Format (0, 0, 6) && Search The Internet (1, 10, 4) && Standard Ebooks (1, 0, 0) && TTS to MP3 (0, 6, 0) && View Manager (1, 10, 2) && Wiki Reader (2, 2, 1) && all recipes Recipe Reader (1, 0, 2) && Overdrive Link Metadata Source (2, 57, 0)
Traceback (most recent call last):
File "calibre_plugins.overdrive_libby.workers", line 432, in run
File "calibre_plugins.overdrive_libby.workers", line 436, in <listcomp>
KeyError: 'parentMagazineTitleId'

I exited & restarted Calibre (I'm running Portable 6.14.1) and this is the first time this problem has occurred. Restarting Calibre didn't fix the issue.

The following day, it was working again, so I'm guessing this was a transient error on Libby's side of things.