For long document text-to-JSON extraction, use bounded review jobs and preserve an explicit incomplete state after a timeout. Chunking must respect the token limit without losing required evidence. A parseable response is insufficient evidence that the review finished.
Short answer: For an edtech service reviewing code changes and returning structured JSON findings, separate request deadlines, token budgets, and evidence coverage. Chunk along source boundaries, account for every required chunk, and validate findings before publishing them. Keep provider adapters behind that application contract so switching providers cannot quietly redefine what a completed review means.
Start the postmortem with one question: what page fired? A timeout alarm tells the responder that a request exceeded a boundary; it doesn't establish whether the document exceeded a context window, retrieval omitted a relevant change, or a response arrived too late to be useful.…