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
- 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.
- 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 · ◷
Fix the
set_issue_fieldcall to stop targeting aStatusfield that no longer exists on the target project board — it deterministically fails thesafe_outputsjob and silently drops the agent's output even though the agent job succeeds.Problem
The agent job completes successfully, but the downstream
safe_outputsjob 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
Evidence (from
audit)(Secondary, non-fatal:
trufflehog_scanloggedArtifact 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
Statusfield (closest isGlobal Status/Release Phase). Theset_issue_fieldsafe-output config in Smoke Codex still referencesStatus, so field-name discovery fails and the whole job exits non-zero.Proposed remediation
set_issue_fieldconfig to a validfield_name(likelyGlobal StatusorRelease Phase), or pinfield_node_idto bypass name discovery.set_issue_fieldnon-fatal (warn + continue) so one bad field write does not sink an otherwise-successful safe-outputs batch.Success criteria
safe_outputsjob completes green with the field write applied (or gracefully skipped).Issue field "..." not founderror in Process Safe Outputs.Parent: #46171. Analyzed run: 29983202629.
Related to #46171