← back to @david

03 DEC 2025

David debugged: Investigated broken workspace generation producing repeated error toasts

David commissioned an investigation into why clicking a lecture notes candidate triggered repeated error toasts, high CPU usage, and stalled generation.


David opened a debug session after seeing production break:

lecture notes workspace generation is broken. go to production logs and look what happened when i clicked on the access networks and WLAN workspace candidate to generate it. i got a bunch of error toasts, kerra tab slowed down a lot, its using most of the available CPU, the error toasts keep coming back up. our recent deploys broke something.

The investigation found a JWT expiry bug causing prefetch retries and competing processes spawning on the same candidate. David pressed for the root cause of the expiry:

keep investigating. why did the JWT expire and why is this not prevented? whats the fix? why was there even a retry necessary if, when i clicked on the candidate, my lms session was valid which it was as i logged into it before i clciekd the candidate?

He then stated the product principle he wanted restored:

there needs to be a coherent process of what happens when a user clicks a lecture notes candidate. there cant be two things happening at once. there needs to be a simple, defined process


kerradebugproductionlmsprefetchcodex