[aw-failures] [aw] Smoke Codex safe_outputs fails — set_issue_field cannot bind to same-batch created issue ("No issue number available")

[github-actions]

Make set_issue_field resolve the issue created earlier in the same safe-output batch — Smoke Codex's safe_outputs job hard-fails when it cannot. A set_issue_field message that follows a create_issue in the same run dies with "No issue number available", turning the whole job red even though the agent succeeded.

Parent report: #39883 (6h failure investigation).

Problem statement

The safe_outputs job of Smoke Codex fails at the Process Safe Outputs step while the agent job succeeds. The agent emits four safe outputs in order — create_issue (1/4), set_issue_field (2/4), add_comment (3/4), comment_memory (4/4). Message 2 (set_issue_field) is rejected because it carries no resolvable issue target, so the processor fails the message and marks the job failure.

Affected workflow and run IDs

Workflow	Run	Result	Failing job/step
Smoke Codex	§27892632179	failure	safe_outputs → Process Safe Outputs

• Branch: copilot/update-conclusion-job-aggregate-data; event: pull_request.
• Agent job conclusion: success (361k tokens). Failure isolated to safe-output processing.

Evidence (job log 1_safe_outputs.txt)

1. Processing message 1/4: create_issue
2. Processing message 2/4: set_issue_field
3. ##[error]✗ Message 2 (set_issue_field) failed: No issue number available
4. ##[warning]1 message(s) failed to process
5. ##[error]1 safe output(s) failed: → job conclusion failure.

Probable root cause

set_issue_field (message 2) targets the issue created by create_issue (message 1), but no issue number is in scope at processing time: the agent did not link the two via a temporary_id, and the processor has no fallback to the just-created issue. Result: the field update cannot bind to a target and the message — and the job — fail.

Proposed remediation (pick one or both)

1. Product: Have set_issue_field resolve a same-batch create_issue target by temporary_id (the canonical #aw_... cross-reference), and reject unbound set_issue_field at emit time with an actionable message instead of failing late in Process Safe Outputs.
2. Smoke prompt: Update smoke-codex.md so the conformance step links set_issue_field to the created issue via temporary_id, exercising the supported contract.

Success criteria / verification

• Smoke Codex safe_outputs job is green: set_issue_field either applies to the intended issue or is rejected at emit time with a clear contract error.
• A regression test covers create_issue → set_issue_field linked by temporary_id in one batch.

References

• §27892632179
  Related to [aw-failures] [aw] Failure Investigation Report — 6h window (2026-06-17 19:34 UTC) #39883

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

• expires on Jun 28, 2026, 12:34 AM UTC-08:00

[github-actions]

🍪 Issue Monster selected this for Copilot

I've 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 · 2.51 AIC · ⌖ 1.72 AIC · ⊞ 5.7K · ◷

[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: 11A0:24EB9B:2AA122F:9C4FFE5:6A37AF2E)