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.
This commit is contained in:
@@ -298,6 +298,9 @@ class FlowRun(SQLModel, table=True):
|
||||
flow: str = Field(index=True, max_length=255)
|
||||
#: What caused it: the work item's cause, "manual", or "run" for a batch.
|
||||
source: str = ""
|
||||
#: The run this one continues: on a rate-limit flush, the run whose value
|
||||
#: the window held back. Empty for everything else.
|
||||
parent: str = Field(default="", max_length=64)
|
||||
started_at: datetime = Field(
|
||||
index=True,
|
||||
sa_type=UTCDateTime,
|
||||
|
||||
Reference in New Issue
Block a user