Premia

Troubleshooting

Common issues and how to resolve them.

A run is stuck in "queued"

Two causes:

  1. It's waiting for a free worker — normal, it'll start shortly.
  2. You're at your plan's concurrency limit. The run is paced (re-queued), not failed, and starts automatically when a slot frees. Concurrency counts top-level runs — see Billing.

"Monthly ticket limit reached"

You've used your plan's included tickets. Free is a hard cap (upgrade to continue); paid plans bill overage per extra ticket. Check Settings → Usage.

"Spend cap reached"

You set a monthly spend cap and this cycle's projected spend hit it. Raise or clear it under Settings → Usage, and paused runs resume.

A ticket didn't trigger a run

  • Confirm the issue has the premia-ready label.
  • Confirm Linear is connected and the webhook is active (Settings → Integrations).
  • Re-apply the label to re-fire the event.

A repo doesn't show up

Make sure the Premia GitHub App is installed on that repo, then Sync the repo list. From the CLI: premia repos list.

A custom agent won't deploy

  • Only code agents deploy; config agents don't.
  • Fix any syntax errors first (deploy is blocked on invalid code).
  • Watch status with premia agents view <slug> or premia agents deploy <slug> --wait.

BYOK model isn't being used

Set the provider key as an org-scope secret with the exact expected name (e.g. ANTHROPIC_API_KEY, OPENAI_API_KEY). More specific scopes (repo/environment) override the org scope — see Models & secrets.

CLI says "Not logged in"

Run premia login, or set PREMIA_TOKEN. Check the target with premia whoami; if you're hitting the wrong backend, re-run premia login --api-url <url>.

CI integration

Run Premia from GitHub Actions and gate on the result.

On this page

A run is stuck in "queued""Monthly ticket limit reached""Spend cap reached"A ticket didn't trigger a runA repo doesn't show upA custom agent won't deployBYOK model isn't being usedCLI says "Not logged in"