{"asOf":"2026-10-03","doesNotChangeDepotPicks":true,"doesNotChangePriceSort":true,"doesNotChangeFreeIndex":true,"note":"Classification and failure modes are mechanisms. Case studies are included only when the source URL was fetched on 2026-10-03. A capability ceiling is not a company incident. Vendor figures are labeled as that vendor's report.","count":1,"catalogCount":27,"refused":["Replit agent database story (July 2025): The Register URL returned HTTP 403 and no first-party engineering postmortem was fetched. Not indexed.","CanLII HTML for 2024 BCCRT 149 returned a client-side block. The Civil Resolution Tribunal document was fetched instead and is the indexed source.","Cursor agent best-practices post loaded and is a product guide, not a postmortem. Not indexed as an incident. The University of Chicago study it mentions was not fetched.","Cognition 'Introducing Devin' (published 2024-03-12) duplicates the SWE-bench technical report. The report is indexed; the launch post is not a second study.","Anthropic many-shot jailbreaking research page loaded. It is an attack writeup, so it is not indexed and no procedure is stored.","OWASP LLM01:2025 was fetched and is cited on the prompt-injection failure mode only. Attack examples from that page are not copied into a case study.","Calder Lab and similar unsourced production-metric blogs were not fetched and are not indexed.","Google Research abstract for Data Cascades in High-Stakes AI loaded on 2026-10-03 (the abstract says 92% prevalence). Not indexed for data-etl: it is an interview study of ML data practice, not a pipeline job failure. The indexed data-etl study is the dbt Cloud status page."],"studies":[{"id":"dbt-cloud-databricks-adapter-arg-2025","title":"dbt Cloud scheduled jobs failed on an unexpected Databricks adapter argument","year":2025,"studyKind":"production_incident","classIds":["data-etl"],"failureModeIds":["schema-drift"],"lesson":"dbt Cloud's status page for EMEA Cell 1 Azure says scheduled jobs for Azure Databricks customers failed with an AdapterGetRelationParams error that named an unexpected argument, needs_information. The page marks the incident identified on Tue, Sep 16, 2025, 05:03 PM, a temporary fix deployed by 05:19 PM the same day, and resolved on Fri, Sep 19, 2025, 04:28 PM. It calls the impact a partial outage of Scheduled Jobs and does not say which component added the argument or name a timezone. A pipeline run that errors on an unexpected argument has not finished the load. Do not mark the job successful because a later update says resolved.","sourceUrl":"https://status.getdbt.com/emea-cell-1-azure/incidents/01K59QNKF7W44ER40KRH1RQJFZ","asOf":"2026-10-03","notes":"Fetched the vendor status page on 2026-10-03. The page does not describe an agent. It does not state a root cause beyond the error string."}]}