dch_002 · Deployment Handler: missing project → 404 with clean message
Status: ✓ Passing · Last run: 2026-06-09T07:14:26 · Pipeline: deployment_handler
· History: 1/1 runs passed (100%)
What was tested
Call handle_render_live against a project_id that was never written to Firestore. Expect HTTP 404 with an error message mentioning the project, NOT a 500 traceback.
What we planted in the data
- 1 entities
- Signal strength: 0.50 (sigmoid slope multiplier)
scenario=missing_project
What the system did
- Model selected:
DeploymentHandlerRunner
What we checked — all assertions passed
| Status | Assertion | Detail |
|---|---|---|
| ✓ | handler_returns_status |
handler returned 404 (body error='project not found') |
| ✓ | handler_error_message_mentions |
handler error mentions 'project' |
How this could have gone wrong
(no assertion descriptions provided)
Why this case matters
When a user opens the Live tab for a project that never existed (link rot, shared link from a since-deleted project), the right answer is a 404 with "project not found" — not a 500 that pages on-call.
Reproducing
# from auto_insight_api/
python -m validation.v2 run dch_002 --pipeline deployment_handler -v
- Case config:
validation/v2/cases/dch_002_missing_project.yaml - Data shape:
deployment_handler_missing_project - Analytics type:
deployment_handler