[AW Top 10] 07 Recover workflows that finish without terminal output #69883

Priority 7/10 | 5 source issues | Impact 3/5 | Confidence 3/5 | Effort 3/5

One assignment, one coherent fix

Several daily workflows end with report_incomplete or without a terminal safe output even though the driver exited cleanly and a safe-output record exists.

Implementation scope

Inspect the failure classification path, treat recorded safe-output persistence as terminal where valid, and ensure the failure handler reports distinct causes instead of unknown.

Done when

• A test shows a run with one persisted safe output is not classified as missing a terminal output.
• Failure issues for unknown driver exits include a specific classification.

Why now

Three recent reports show the same completion-detection symptom across unrelated workflows, though root causes may differ per run.

Unchanged AW sources close only after this summary is completed. Newer source activity and not-planned retirement do not trigger source closure. Assigned summaries are frozen; unassign to allow reclustering.

Generated by AW Essential Issue Clustering · copilot · auto · 21.6 AIC · ⌖ 0.616 AIC · ⊞ 8.9K · ◷