← back to @david

15 JAN 2026

David's problem: PDF viewer overlay failed to load on clicked inserted pages

David reported that clicking an inserted PDF page in a workspace opened a viewer overlay that then failed to load, despite the file having been successfully prefetched.


David investigated why the PDF viewer overlay was failing after kerra had successfully inserted all the pages into the workspace.

no, this is not about filtering out broken files because the files are not broken, and them being marked as broken is a bug. how can they be broken if im literally looking, with my own eyes, at the inserted pdf pages of the file in the lecture that kerra made? kerra literally inserted every page of the file into the blocknote editor document. that means kerra successfully accessed the file, and we successfully prefetched it from the users lms by downloading it through their extension and should have persisted it on s3. so what on earth is actually going on?

David's reasoning was sound — if the pages were visible in the editor, the file was in S3 and the broken-file flag was wrong. The agent's initial suggestion to filter out broken files was treating the symptom, not the cause.


kerrapdf-viewerdebugs3prefetchworkspacecodex