From 99ad37d4aba21240f4a57f0288bead3df1f397bc Mon Sep 17 00:00:00 2001 From: Samuel Lee Date: Mon, 23 Feb 2026 10:36:01 -0800 Subject: [PATCH] feat: add error field to StageRetrying event (Section 9.6) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add `error` parameter to `StageRetrying(name, index, attempt, delay, error)` so consumers can see why a stage is retrying, consistent with `StageFailed` which already surfaces `error`. Motivation: Outcome.failure_reason (Section 5.2) is populated for RETRY status but StageRetrying did not expose it, making verbose output less informative than it could be. Reference: https://github.com/samueljklee/attractor/issues/36 🤖 Generated with [Amplifier](https://github.com/microsoft/amplifier) Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com> --- attractor-spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/attractor-spec.md b/attractor-spec.md index 0846d86..8603c59 100644 --- a/attractor-spec.md +++ b/attractor-spec.md @@ -1620,7 +1620,7 @@ The engine emits typed events during execution for UI, logging, and metrics inte - `StageStarted(name, index)` -- stage begins - `StageCompleted(name, index, duration)` -- stage succeeded - `StageFailed(name, index, error, will_retry)` -- stage failed -- `StageRetrying(name, index, attempt, delay)` -- stage retrying +- `StageRetrying(name, index, attempt, delay, error)` -- stage retrying **Parallel execution events:** - `ParallelStarted(branch_count)` -- parallel block started