FAQ

Create a fresh API token (Account → API tokens), run spanline auth login again, and confirm spanline auth workspace use (or auth workspace list) points at the right workspace. In CI, check SPANLINE_TOKEN and SPANLINE_WORKSPACE.

I get signed out or “unauthorized” from the CLI

Enterprise self-host: release binaries default to Spanline Cloud. Set --api https://api.<your-domain> on login or SPANLINE_API in CI so the CLI talks to your install — see Run tests § Enterprise self-host.

Overview shows “No runs yet”

That empty state appears until a runner uploads results. Create a scenario under Performance → Scenarios, then run it with the CLI (spanline test run …). Inventory KPIs can show scenarios/collections even when runs are still zero. After seeding or real traffic, Overview fills with pass rate, recent runs, and collection-run progress. See Getting started.

The run stays “running” forever

Check that the CLI/CI job is still alive and that k6 started. Abort from the app if you need to stop; start a new run afterward.

Collection run stays “pending”

Start run only creates a plan. A runner must execute it (spanline test collection-run --id … or test watch after a webhook). Confirm the collection-run id in the execution drawer and that CI has the right workspace token.

“k6 not found”

Install k6 on the machine or allow the CLI to download it. In restricted CI, install k6 in the image ahead of time (or use --no-install-k6 only after k6 is present).

Run rejected because of quota

Your organization plan may cap monthly runs. Ask an admin or wait for the next period.

Compare shows nothing useful

Both runs must belong to the same workspace and should have finished with summaries uploaded. Open Performance → Compare and pick finished Baseline (A) and Candidate (B). You can also enter from a finished run’s Compare control or Matrix as A.

Empty matrix

Confirm the collection run completed and that child jobs produced results. Re-export after the run finishes. You can deep-link with ?collectionRunId=. App export is Export CSV; use CLI test matrix --format json for JSON.

I do not see Metrics / Artifacts / Infra tabs

Those tabs appear on finished runs. Live runs focus on the Summary streaming view. Infra stays empty unless collectors recorded snapshots for that run.

Artifact upload failed

Files may exceed the size limit. Upload a smaller bundle or split logs. Use --upload-artifacts only when you need the files attached to the run. Header Download is summary JSON, not the artifact zip.

Connection test failed

Check the URL and token in Performance → Connections. If the value is sealed, re-enter it after a key change.

Sealed secret errors after rotation

CI or your laptop may still be using an old organization private key. Ask an admin for the current key setup (SPANLINE_ORG_RSA_PRIVATE_KEY / file path).

Webhook did nothing

Confirm the webhook secret header matches the value from the collection editor, and that a runner is available to pick up the collection plan (spanline test collection-run / test watch as your pipeline requires). Managing webhooks usually needs admin/owner.

Cron did not fire

Collection cron fields are metadata only today — Spanline does not run the schedule yet. Use external CI or spanline test watch until registered runners ship.

Environments vs Performance rail

Environments are under Workspace → Environments (/workspaces/environments), not a tab inside the Performance product rail. Scenarios attach to those environments when you edit them.

Project filter does nothing

Link a Project on the scenario or collection, then choose it in the toolbar Project · All control on Scenarios/Collections. The filter is personal to your browser for that workspace.

Symptom Likely cause Fix
Matrix is empty but runs exist No collection-run batch — jobs ran separately Use Reports → Collection window with collection + dates
Reports shows gaps Expected — scenario had no run in the window Run missing scenarios or widen From / To
Trends shows UUIDs or wrong env Stale rollups or old API Rebuild rollups (admin); refresh after server update
Trends empty No finished runs in range, or rollups not built Finish a run; Rebuild rollups for historical data
Need proof for one release gate Trends is the wrong tool Matrix (one batch) or Reports (date window)

Full comparison: Concepts → which view?.

Reports — collection window (separate schedules)

When scenarios in a collection ran at different times (not one collection-run batch), use Performance → Reports → Collection window:

  1. Pick the collection
  2. Set from / to dates
  3. Review runs and gaps (scenarios with no run in the window)
  4. Export CSV or Save snapshot for audit

Matrix remains the right view when you executed spanline test collection-run once and need per-job evidence for that run.

Trends roll up finished runs (passed / failed) per day. If you just imported old runs or changed data, open Trends and click Rebuild rollups (workspace admin) for the date range you need. Otherwise finish at least one run in the window and refresh.

Public report unlock or embed

Symptom Likely cause Fix
Unlock says password incorrect Wrong or outdated password after Rotate Ask owner for the current password from Embed & share (active shares can reopen credentials)
View URL fails immediately Link revoked or wrong gate token Owner creates a new public link from Embed & share
Embed iframe blank / expired message 24h embed token expired Open the view URL again and unlock to get a fresh embed
No embed URL in owner popover By design — embed is issued on unlock Recipient (or owner testing) unlocks on /p/r/view/…
Expecting a modal snapshot Viewer is a dedicated page now Use Open → /performance/reports/view/{id}
Workspace embed works but public does not Different paths and auth Workspace: /performance/reports/embed/{id} + sign-in; public: unlock flow above

Detail: Reports & sharing.

Scripts / Thresholds tabs

Those rail entries are marked Soon and are not available yet. Use Scenarios (including Gates), Runs, Compare, Matrix, Reports, and Trends for current workflows.