Skip to content

Deploy fails with resource_exhausted despite no quotas being exceeded (Free plan) #3020

@MajorAaron

Description

@MajorAaron

Bug Description

CLI and GitHub-triggered deploys consistently fail with [resource_exhausted] Project quota exceeded for your org, please upgrade your plan to increase, despite no quotas being exceeded on the dashboard.

Error Message

X Error: Failed to start deployment: Internal server error: [resource_exhausted] Project quota exceeded for your org, please upgrade your plan to increase

Environment

  • CLI version: trigger.dev@4.3.3
  • SDK version: @trigger.dev/sdk@4.3.3
  • Plan: Free
  • Project ref: proj_dwrtapnblfwizjauvzgs
  • Org slug: pipelines-3b9e
  • Region: us-east-1 (default)
  • OS: macOS (Darwin)

What I've Verified on the Dashboard

Quota / Setting Value
Projects 1 of 10
Team members 1 of 5
Monthly usage $0.00 of $5.00
Concurrent runs 0 of 20
Schedules 0 of 10
Alert channels 0 of 1
Region us-east-1 configured as default
Native build server Enabled
GitHub integration Connected, main → Production

No quotas are at or near their limits.

Reproduction Steps

  1. Created a project on the Free plan
  2. Connected GitHub repo (MajorAaron/golden-eye-pipelines) via the GitHub app
  3. Set Production branch to main
  4. Run npx trigger.dev@latest deploy --env prod
  5. Build succeeds locally (Containerfile generated, env vars synced)
  6. Fails at "start deployment" API call with resource_exhausted

The same error also blocks GitHub-triggered auto-deploys — the Deployments page shows "Waiting for tasks to deploy" despite multiple pushes to main.

Additional Context

  • The error alternates between [resource_exhausted] Project quota exceeded and [aborted] read ECONNRESET on some attempts, suggesting possible server-side instability.
  • Enabling "Use native build server" in Project Settings did not resolve the issue.
  • The build completes successfully every time — only the remote deployment initiation fails.
  • The Trigger.dev status page shows all services Operational, but the API uptime chart shows a recent blip.
  • This is a brand new project with zero prior deployments in any environment.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions