GitHub Actions steps.<id>.outputs Empty - Missing or Wrong Step id

By Kaveh Alemi·Latchkey

A later step reads steps.<id>.outputs.<name> and gets an empty string because the producing step has no id, the id is misspelled, or the reference points at a step that has not run yet.

What this error means

An expression that should carry a value from an earlier step evaluates to empty. The workflow compiles fine, but downstream logic behaves as if the output was never set.

- run: echo "tag=v1.2.3" >> "$GITHUB_OUTPUT"   # no id on this step
- run: echo "${{ steps.meta.outputs.tag }}"   # prints empty

Common causes

Producing step has no id

steps.<id> only resolves for a step that declared an id. A step that writes to GITHUB_OUTPUT without an id cannot be referenced by any later step.

Typo or wrong id referenced

The id in the expression does not match the producing step exactly, or it refers to a step in a different job that the steps context cannot reach.

How to fix it

Give the producing step an id and reuse it

- id: meta
  run: echo "tag=v1.2.3" >> "$GITHUB_OUTPUT"
- run: echo "Tag is ${{ steps.meta.outputs.tag }}"

Confirm scope and ordering

1. The reference must come after the producing step within the same job.
2. For cross-job values, use job outputs and the needs context instead of steps.
3. Match the id and output name exactly, including case.

How to prevent it

• Always add an id to any step whose outputs you consume.
• Use needs.<job>.outputs for cross-job data, steps.<id> only within a job.
• Echo the value once while wiring it up to confirm it is populated.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions