[aw-failures] [aw] Smoke Copilot safe_outputs job fails — dispatch_workflow to "haiku-printer" omits required 'message' input (H [Content truncated due to length]

[github-actions]

Problem statement

The safe_outputs job of Smoke Copilot fails at the Process Safe Outputs step even though the agent job succeeds and 9 of 10 other safe outputs are applied. The failure is caused by a single dispatch_workflow safe output that targets haiku-printer without supplying that workflow's required message input. The GitHub dispatch API rejects it with HTTP 422, and the handler marks the whole job as failed.

Affected workflows and run IDs

Workflow	Run	Result	Failing job/step
Smoke Copilot	§27885948833	failure	safe_outputs → Process Safe Outputs

• Branch: fix/code-scanning-600-unsafe-quoting-3e48605690b14101; event: workflow_dispatch.
• Agent job conclusion: success (37 turns, 2.20M tokens). Failure is isolated to safe-output processing.

Evidence (log references, job 82521927044)

1. Processing message 2/14: dispatch_workflow → Dispatching workflow: haiku-printer.yml
2. POST /repos/github/gh-aw/actions/workflows/haiku-printer.yml/dispatches - 422
3. ##[error]Failed to dispatch workflow "haiku-printer": Required input 'message' not provided
4. ##[error]✗ Message 2 (dispatch_workflow) failed: ...
5. ##[warning]1 message(s) failed to process followed by ##[error]1 safe output(s) failed: - dispatch_workflow: ... → job conclusion failure.

Other outputs in the same run succeeded (created issue #40526, discussion #40525, discussion comment on #40516, artifact upload), confirming the failure is specific to the dispatch input contract.

Probable root cause

1. .github/workflows/haiku-printer.yml declares workflow_dispatch.inputs.message with required: true (lines 4-8).
2. The Smoke Copilot dispatch-workflow safe-output config (.github/workflows/smoke-copilot.md, lines 105-109) lists only workflows: [haiku-printer] with no inputs mapping.
3. The prompt (smoke-copilot.md step 11) instructs the agent to dispatch haiku-printer "with an original testing/automation haiku," but the emitted dispatch_workflow item carried no message field, so no required input reached the dispatch API.
4. The dispatch_workflow handler dispatches before validating that required workflow inputs are present, so a recoverable per-message problem escalates to a hard job failure.

Proposed remediation (any one resolves the failure; 1+2 recommended)

1. In smoke-copilot.md, make the message input explicit/deterministic for the dispatch-workflow output (e.g. supply a default inputs.message or instruct the agent to always include a non-empty message), so required inputs are guaranteed.
2. In the dispatch_workflow safe-output handler, pre-validate that all required: true inputs of the target workflow are present and fail the individual message gracefully (skip + warn) rather than 422-ing the API and failing the whole job — mirror the existing "skipped" handling used for create_pull_request_review_comment in this same run.
3. Alternatively, relax haiku-printer.yml message to required: false with a default, since it is a test target.

Success criteria / verification

• A re-run of Smoke Copilot completes with safe_outputs job conclusion success.
• The haiku-printer dispatch either succeeds (200/204) with a populated message, or is skipped with a warning instead of failing the job.
• No 1 safe output(s) failed: dispatch_workflow error in the Process Safe Outputs step.

Correlation / scope

• Not covered by any existing open agentic-workflows issue (no issue references dispatch_workflow/haiku-printer).
• Sub-issue of failure-investigation parent [aw-failures] [aw] Failure Investigation Report — 6h window (2026-06-17 19:34 UTC) #39883. Other failures in the 6h window are already tracked: Avenger "Parse agent logs" ([aw-failures] [aw] Avenger agent job fails at "Parse agent logs" — ERR_CONFIG "no structured log entries" despite successful age [Content truncated due to length] #40145), Skillet startup-failures ([aw-failures] [aw] Skillet floods Actions with startup-failures on copilot/* branch pushes (recurring — 73 failed runs / 6h as o [Content truncated due to length] #40447).

References: §27885948833
Related to #39883

Generated by 🔍 [aw] Failure Investigator (6h) · 216.2 AIC · ⌖ 12.5 AIC · ⊞ 4.9K · ◷

• expires on Jun 27, 2026, 5:48 PM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I have identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · 3.7 AIC · ⌖ 1.72 AIC · ⊞ 5.8K · ◷

[copilot-swe-agent]

The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists. (Request id: 1A00:5B38B:1CD7071:6A7EBF9:6A374CAE)