Operations console
Cross-tenant reads for operators. Every panel is served by /v1/admin, which refuses any credential without the operator scope — this page carries no privileges of its own.
Operator credential
A dashboard login is used automatically. Otherwise paste an access token; it is held in this tab only, never stored. An API key will authenticate and then be refused by every panel below, whoever issued it.
No credential set.
Feedback inbox
Everything customers have sent through the dashboard, newest first. The only panel here that needs no selector — it is the question rather than the answer. Notes and todos are shared: every operator sees every operator's.
Datasets
Off-the-shelf editions and the accounts that hold them. A grant opens its edition and every smaller edition of the same release, with no keys or manifests for the customer to handle. Revoking takes effect on their next request; links already handed out lapse within the hour they were signed for.
Account
Signup time, verification state, invite attribution, and per-service remaining quota for each tenant the account belongs to.
Fill exactly one. The user ID is what the task table below prints for every request, so a task's User cell is a link straight into this panel.
Requests
Processing requests for one tenant, newest first, with every task inline: service, age, state, retry linkage and failure code.
Fill exactly one. A task ID answers with the whole request it belongs to, whichever tenant that is, so a customer's identifier is enough to start.
Unsupported phone regions
Accounts whose number is in a country we cannot send a verification
passcode to yet. They are let in unverified and told verification is coming. Registering a
country’s SMS sender and adding it to GSI_SMS_SUPPORTED_REGIONS gates
these accounts until they verify. Click a country to see its accounts.
Lanes
Queued, active and overdue work per lane. Queued is ACCEPTED — submitted, not yet dispatched — plus QUEUED — dispatched, but its worker has not claimed it on a node yet; it climbing while active stays flat is a stalled dispatcher or a node that never boots, and it is the only column that moves for the first six hours of one, because nothing is overdue until its own deadline passes. Counts come from a capped sample and say so when they hit the cap.
Warm nodes
One node per lane at a time, kept up so jobs skip the few-minute boot. A lane can have several windows booked ahead, as long as they do not overlap; each launches its own node at its start time (Pacific), ready a few minutes later. As soon as a node is up it runs one short clip as an ordinary job (charge waived, in the warmup account), so the first real job finds it warm; the Warmup column shows how that went. Leave the start blank to launch now. The start and shutdown times are enforced server-side whether or not this page is open. A node runs its lane's default release as of launch and takes jobs until it shuts off; a job still running then restarts on a node of its own. Without a warm node, jobs launch their own node as usual. While a node is up this panel updates itself.
Live
Log