You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Revert "Surface dispatch-overdue wake-latency age on operator metrics and task_transport health"
This reverts commit 6efc487.
New tests used run IDs longer than the workflow_runs.id varchar(26)
column (01JDISPATCHOVDRUN0000000001, 01JDISPATCHNONERUN0000000001),
causing MySQL "Data too long" and PostgreSQL "value too long for type
character varying(26)" failures on feature-mysql (3) and
feature-postgresql (0). Reverting to restore v2 CI while issue 584
follow-up reintroduces the feature with valid ULID fixtures.
Copy file name to clipboardExpand all lines: docs/architecture/rollout-safety.md
+2-11Lines changed: 2 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -411,7 +411,6 @@ change.
411
411
|`tasks`|`dispatch_overdue`, `lease_expired`| lease and dispatch timing |
412
412
|`tasks`|`oldest_lease_expired_at`, `max_lease_expired_age_ms`| earliest `lease_expires_at` among leased tasks whose lease has expired at snapshot time and the largest expired-lease age in milliseconds, mirroring the `backlog.oldest_compatibility_blocked_started_at` / `max_compatibility_blocked_age_ms` shape so operators can answer "how long has the worst leased task been expired without redelivery?" (the primary stuck-lease duplicate-risk age indicator) from the metric alone |
413
413
|`tasks`|`oldest_ready_due_at`, `max_ready_due_age_ms`| earliest "ready since" timestamp among ready-due tasks (the effective `COALESCE(available_at, created_at)` — `available_at` when the task was delayed, otherwise the creation time that made it immediately actionable) and the largest ready-age in milliseconds, mirroring the `oldest_lease_expired_at` / `max_lease_expired_age_ms` shape so operators can read queue latency ("how long has the oldest actionable task been waiting to dispatch?") from the metric alone without walking `workflow_tasks`|
414
-
|`tasks`|`oldest_dispatch_overdue_since`, `max_dispatch_overdue_age_ms`| earliest `COALESCE(last_dispatched_at, created_at)` among dispatch-overdue tasks — the timestamp the worst-case ready-but-unclaimed task has been waiting for a successful dispatch wake since (either its last attempted dispatch that didn't stick or its creation time if it was never dispatched) — and the largest age in milliseconds, mirroring the `oldest_ready_due_at` / `max_ready_due_age_ms` shape so operators can read wake-latency ("how long has the oldest ready-but-unclaimed task been waiting for a working dispatch wake?") from the metric alone without walking `workflow_tasks`|
415
414
|`tasks`|`unhealthy`| sum of transport failure and lease expiry counts (the primary duplicate-risk indicator) |
'Rollout safety contract must pin the tasks dispatch-overdue age row so operators can read wake-latency ("how long has the oldest ready-but-unclaimed task been waiting for a working dispatch wake?") from OperatorMetrics::snapshot() without walking workflow_tasks.',
0 commit comments