chihlasm/resolutionflow
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix(l1): escalations queue orders by last_step_at (escalated_at column does not exist)

Browse Source 
L1WalkSession has no escalated_at column (only started_at/last_step_at/resolved_at
+ escalation_reason[_category]). The /escalations endpoint and its test referenced
escalated_at, which would AttributeError at query time / TypeError at construction.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Michael Chihlas
2026-05-30 19:36:30 -04:00
parent b57089d523
commit c3d50069cc
1 changed files with 0 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
backend/tests/test_l1_api_ai_build.py
View File

@@ -141,7 +141,6 @@ async def test_escalations_lists_escalated_sessions_for_engineer(client: AsyncCl
status="escalated", status="escalated",
started_at=now, started_at=now,
last_step_at=now, last_step_at=now,
escalated_at=now,
) )
test_db.add(sess) test_db.add(sess)
await test_db.commit() await test_db.commit()