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:
@@ -4777,6 +4777,11 @@ export const fluksio__api__routes__observability__RunRowSchema = {
|
||||
type: 'string',
|
||||
title: 'Source'
|
||||
},
|
||||
parent: {
|
||||
type: 'string',
|
||||
title: 'Parent',
|
||||
default: ''
|
||||
},
|
||||
status: {
|
||||
type: 'string',
|
||||
title: 'Status'
|
||||
|
||||
@@ -506,6 +506,7 @@ export type fluksio__api__routes__observability__RunRow = {
|
||||
id: string;
|
||||
flow: string;
|
||||
source: string;
|
||||
parent?: string;
|
||||
status: string;
|
||||
started_at: string;
|
||||
finished_at?: (string | null);
|
||||
|
||||
Reference in New Issue
Block a user