# 21_percona_eks_hardened#1 — FAILED | field | value | |---|---| | campaign | COVERAGE (mongodb × aws) | | archetype | generative | | date | 2026-10-14T12:00Z | | gate version | v1 | | deployment | None | | deploy status | None (1532s) | | gate | healthz=— connection=— logs=— metrics=— | | teardown clean | False | ## Attribution - **bucket:** PLATFORM - **class:** request-assembly-400 - **evidence:** The chat never reached a deployment. Two request-assembly defects in the platform's session engine surfaced with a newer model generation: (1) a turn that waited on the session lock refreshed its history from the store and dropped the message it had just been handed, so the request ended with an assistant message and the provider refused it (137 occurrences across the campaign; older models had continued silently, never seeing the dropped message); (2) thinking blocks the engine never asked for were stored and replayed, and once the history had been disturbed every later turn was refused. No cloud resource was created. - **resolution:** Fixed (8854538d): a refreshed history keeps the tail it was handed, thinking blocks are stripped on replay, and a request that would end with an assistant message gets a continuation. Scenario 21 passed on its 30 Oct re-run. ## Recorded reason (scrubbed) ``` chat never converged to a deploy: chat did not reach the deploy gate (no deployment_id) ```