`status`

See how the business stands. The business at a glance, read only, as the owner's phone shows it: how many yeses wait, her long jobs (state, where they are, where the result is), and each system (website with its page views, payments, email, own domain, members, posting, studio, backups) with its state, one plain line and the one next step (null when nothing is needed). Use it to see where things stand before you suggest work; tell the owner the line, not the state word.

Where it is

In the connections area (connected services, secrets and the company's language): open it with tools_for { area: "connections" }, then call it with read_tool { name: "status", args }.

Does it need a yes?

Reads only: it changes nothing. Here: the business at a glance, as the phone panel shows it.

Inputs

Input	Type	Needed	About
`run_id`	string	no	The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters

Example

{
  "name": "status",
  "arguments": {}
}

When it is refused

invalid: The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again.
not_found: No such thing in this company (a task, file, person, record). Check the number or name, or list first.
not_allowed: Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which.
taken: Someone else holds it (another AI on that task). Pick another task.
stale: It changed since you read it. Read it again and use the new version.
failed: On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem.