[aw-failures] [aw-fix] P1: Smoke Codex — set_issue_field targets nonexistent project field "Status", failing Process Safe Output [Content truncated due to length]

[github-actions]

Fix the set_issue_field call to stop targeting a Status field that no longer exists on the target project board — it deterministically fails the safe_outputs job and silently drops the agent's output even though the agent job succeeds.

Problem

The agent job completes successfully, but the downstream safe_outputs job fails at Process Safe Outputs. One safe-output message (set_issue_field) is rejected because the requested field is not on the board.

Affected workflows / runs

Workflow	Run	Agent job	safe_outputs job
Smoke Codex	§29983202629	success	failure

Evidence (from audit)

✗ Message 2 (set_issue_field) failed: Issue field "Status" not found.
Available fields: Visibility, Priority, Impact, Effort, DRI, Start Date, Target Date,
Trending, Engineering Staffing, Ship Date Confidence, Release Phase, Release Tier,
Product Pillar, Last Report Date, Strategic Classification, Workstream, Workstream Track,
Release Visibility, Global Status. Use a listed field_name or provide field_node_id to bypass discovery.
1 safe output(s) failed:

(Secondary, non-fatal: trufflehog_scan logged Artifact not found for name: repo-memory-default — unrelated to the job failure.)

Probable root cause

Project-board field drift. The board no longer exposes a Status field (closest is Global Status/Release Phase). The set_issue_field safe-output config in Smoke Codex still references Status, so field-name discovery fails and the whole job exits non-zero.

Proposed remediation

1. Update the set_issue_field config to a valid field_name (likely Global Status or Release Phase), or pin field_node_id to bypass name discovery.
2. Consider making a single failed set_issue_field non-fatal (warn + continue) so one bad field write does not sink an otherwise-successful safe-outputs batch.

Success criteria

• Smoke Codex safe_outputs job completes green with the field write applied (or gracefully skipped).
• No Issue field "..." not found error in Process Safe Outputs.

Parent: #46171. Analyzed run: 29983202629.
Related to #46171

Generated by 🔍 [aw] Failure Investigator (6h) · age00 171 AIC · ⌖ 37.9 AIC · ⊞ 3.8K · ◷

• expires on Jul 29, 2026, 11: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 · gpt54 7.44 AIC · ⌖ 7.48 AIC · ⊞ 7.4K · ◷