Bug Report
Summary
The dispatch_workflow safe-output handler does not resolve #temporary_id references in the inputs map before dispatching the target workflow. The literal string (e.g., #aw_slosync) is passed as the workflow input instead of the resolved issue number.
Reproduction
Parent workflow (slo-sync):
- Creates an issue with
"temporary_id": "aw_slosync" via create_issue
- Framework correctly registers the mapping:
aw_slosync → github/authentication#6499
- Dispatches
create-pr with "issue_number": "#aw_slosync" in the dispatch_workflow inputs
Expected: The framework resolves #aw_slosync to 6499 before dispatching, so the create-pr workflow receives issue_number: "6499".
Actual: The literal string #aw_slosync is passed as the issue_number input. The create-pr workflow prompt interpolates this as ${{ github.event.inputs.issue_number }} → #aw_slosync, which is not a valid issue number.
Impact
In the dispatched create-pr workflow, the add_comment safe output fails because item_number resolves to the invalid string #aw_slosync:
##[error]✗ Message 2 (add_comment) failed: Target is "*" but no item_number/issue_number specified in add_comment item
Evidence
Workflow source
The slo-sync.md prompt explicitly documents this expectation:
Emit a dispatch_workflow safe output to trigger the create-pr workflow. Use #aw_slosync to reference the tracking issue number — the framework resolves temporary IDs to real issue numbers before dispatching.
{
"type": "dispatch_workflow",
"workflow": "create-pr",
"inputs": {
"issue_number": "#aw_slosync",
...
}
}
Expected fix
The dispatch_workflow handler should iterate over all input values and resolve any #temporary_id references using the registered temporary ID map before triggering the workflow dispatch.
Version
gh-aw v0.67.4
Bug Report
Summary
The
dispatch_workflowsafe-output handler does not resolve#temporary_idreferences in theinputsmap before dispatching the target workflow. The literal string (e.g.,#aw_slosync) is passed as the workflow input instead of the resolved issue number.Reproduction
Parent workflow (
slo-sync):"temporary_id": "aw_slosync"viacreate_issueaw_slosync → github/authentication#6499create-prwith"issue_number": "#aw_slosync"in thedispatch_workflowinputsExpected: The framework resolves
#aw_slosyncto6499before dispatching, so thecreate-prworkflow receivesissue_number: "6499".Actual: The literal string
#aw_slosyncis passed as theissue_numberinput. Thecreate-prworkflow prompt interpolates this as${{ github.event.inputs.issue_number }}→#aw_slosync, which is not a valid issue number.Impact
In the dispatched
create-prworkflow, theadd_commentsafe output fails becauseitem_numberresolves to the invalid string#aw_slosync:Evidence
slo-sync run: https://github.com/github/authentication/actions/runs/24256002896 (succeeded)
aw_slosync -> github/authentication#6499create-pr.lock.yml (run ID: 24256231535)create-pr run: https://github.com/github/authentication/actions/runs/24256231535 (failed)
"item_number": #aw_slosync,(not resolved)create_pull_requestsucceeded → github/slo-bot#653add_commentfailed → missing validitem_numberWorkflow source
The
slo-sync.mdprompt explicitly documents this expectation:{ "type": "dispatch_workflow", "workflow": "create-pr", "inputs": { "issue_number": "#aw_slosync", ... } }Expected fix
The
dispatch_workflowhandler should iterate over all input values and resolve any#temporary_idreferences using the registered temporary ID map before triggering the workflow dispatch.Version
gh-aw v0.67.4