Unable to process file command CI/CD Origin: Build & delivery Last updated 25 Oct 2026

GitHub Actions: Error: Unable to process file command 'output' successfully. Invalid format 'x'

A line written to $GITHUB_OUTPUT, $GITHUB_ENV or $GITHUB_STATE is not in name=value form — usually a multi-line value without a delimiter.

Exact message you may see Unable to process file command 'output' successfullyUnable to process file command 'env' successfullyInvalid formatInvalid environment variable formatUnable to process file command 'state' successfully
Seen on: GitHub Actions

Meaning

These files accept NAME=value for single lines and NAME<<DELIMITER … DELIMITER for multi-line values. A value that contains a newline (a file's content, JSON, a commit message) breaks the format. Use a heredoc delimiter, or encode the value.

Common causes

  • Multi-line value written as a single name=value line
  • Value containing a newline from $(cat file) or command output
  • Missing = between name and value
  • Delimiter text appearing inside the value
  • Windows line endings in the written text

⚡ Quick fix

  1. Use the delimiter syntax: name<<EOF … EOF
  2. Write JSON in one line (jq -c)
  3. Use a random delimiter when the value could contain EOF

Detailed fix by platform

GitHub Actions

  1. { echo "notes<<$EOF"; cat notes.md; echo "$EOF"; } >> "$GITHUB_OUTPUT" after EOF=$(openssl rand -hex 8)

Code examples

Multi-line output

yaml
- id: notes
  run: |
    EOF=$(openssl rand -hex 8)
    {
      echo "body<<$EOF"
      git log -5 --pretty=format:'%s'
      echo
      echo "$EOF"
    } >> "$GITHUB_OUTPUT"
- run: echo "${{ steps.notes.outputs.body }}"

How to diagnose

  1. File — output, env or state?
  2. Value — Contains newlines?
  3. Syntax — name=value or heredoc?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):

API rate limit exceeded — GitHub Actions: HttpError: API rate limit exceeded for installation ID 123456 / secondary rate limit (CI/CD)API rate limit exceed…Cache not found / Unable to reserve cache — GitHub Actions: Cache not found for input keys: npm-Linux-abc123 / Failed to save: Unable to reserve cache with key, another job may be creating this cache (CI/CD)Cache not found / Una…Credentials could not be loaded — GitHub Actions: Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers (CI/CD)Credentials could not…Invalid workflow file — GitHub Actions: Invalid workflow file: .github/workflows/ci.yml#L12 — You have an error in your yaml syntax on line 12 (CI/CD)Invalid workflow fileMatrix vector does not contain any values — GitHub Actions: Matrix vector 'node' does not contain any values / Error when evaluating 'strategy' for job (CI/CD)Matrix vector does no…set-output command is deprecated — GitHub Actions: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files (CI/CD)set-output command is…The set-env command is disabled — GitHub Actions: Error: Unable to process command '::set-env name=X::y' successfully. The `set-env` command is disabled (CI/CD)The set-env command i…Unable to download artifact — GitHub Actions: Error: Unable to download artifact(s): Artifact not found for name: build (CI/CD)Unable to download ar…Unable to…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.