c8a82e795b
When the engine hard-cancels in-flight work during a pause/resume cycle and the workflow graph run ends with the task re-queued to `todo`, the executor used to leave it for a fresh scheduler dispatch and fire a spurious failure notification. It now continues the agent session in place via a bounded internal retry (reusing the graph-resume retry budget + backoff), falling back to the benign todo re-queue only after retries are exhausted. - Scoped strictly to engine-internal aborts via a typed `isEngineInternalAbort` discriminant; genuine user/global/task pauses are never auto-resumed. - Re-checks the task at retry fire time and aborts the auto-continue if it was paused, moved, or deleted during the backoff window. - Clears any stale `failed` status and emits an `Auto-recovered:` log so the deferred failure notification is suppressed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
841 B
@runfusion/fusion
| @runfusion/fusion |
|---|
| patch |
Auto-continue the agent session after an engine-internal pause/resume abort instead of re-queueing the task to todo. When the engine tears down in-flight work (hard-cancel) and the workflow graph run ends with the task back in todo, the executor now retries the agent session in place — bounded by the existing graph-resume retry budget with backoff, falling back to a benign re-queue only after retries are exhausted. Before re-dispatching, it re-checks the task at fire time and aborts the auto-continue if the task was paused, moved, or deleted during the backoff window, so genuine user/global/task pauses are never resumed against the operator's intent. The transient reclassification clears any stale failed status and emits an Auto-recovered: log so no spurious failure notification fires.