Report which simulated accounts are actually running
Performs, once and on demand, the comparison the scheduler makes every second: what should be running, against what the connection bucket says is. observed counts every tenant’s runners by state and carries no tenant. test_accounts lists the caller’s simulated accounts, each with what the bucket says about it, and only simulated accounts: for a live account the scheduler additionally requires the organization’s live trading entitlement, which this service does not check, so comparing one here would report a billing exclusion as a missing runner. Bucket entries expire sixty seconds after the last heartbeat, so an absent runner means nothing has reported within the minute rather than that none exists, and checked_at is when the bucket was read. Readable by a client credential holding the credential:read scope, which sees every organization’s simulated accounts, and by an organization admin of a configured internal organization, which sees its own.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Response
What is running, against what should be
The reconciliation the scheduler performs every second, reported once.
When the bucket was read.
Returned rather than left to the caller's clock because every state here
is relative to the bucket's sixty second expiry, and a reader working
out staleness from its own now would be measuring its own latency into
the answer.
Enabled accounts in test_accounts that nothing is running.
Every tenant's runners, counted by state. No tenant in it.
Disabled accounts in test_accounts that something still is.
The caller's simulated accounts, each with what the bucket says.
Test accounts only, and that is a correctness boundary rather than an omission. See the handler for why real trading accounts are not compared here.