Give a rate-limit flush its own run, linked to the run that held the value

A flush ran its cascade under no id, so its executions and failures belonged
to no run. It now records a run with source "flush", and the holding run's id
travels on the queue item into a new `flow_run.parent` column, also on the
`/observability/runs` rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx
This commit is contained in:
2026-10-15 09:37:30 +02:00
co-authored by Claude Opus 5.5
parent c7e38a8a44
commit 13567f8990
10 changed files with 157 additions and 26 deletions
+1
View File
@@ -291,6 +291,7 @@ class MetricsCollector:
"id": run_id,
"flow": str(event.get("flow") or "")[:NAME_MAX],
"source": str(event.get("cause") or ""),
"parent": str(event.get("parent") or "")[:64],
"started_ts": ts,
"started_at": datetime.fromtimestamp(ts, UTC),
"finished_at": None,