`update_work`

Update work. Report progress on a work item.

Where it is

In the work area (showing long media work in the hub): open it with tools_for { area: "work" }, then call it with use_tool { name: "update_work", args }.

Does it need a yes?

Runs at once, no yes card: it changes only the office's own working state, and nothing reaches anyone. Here: a progress card.

Inputs

Input	Type	Needed	About
`workId`	string	yes	Work item id from start_work · format `^[a-z0-9][a-z0-9-]{5,63}$`
`step`	string	no	1 to 200 characters
`progress`	number	no	How far, as a fraction from 0 to 1 (0.5 is half way) · 0 to 1
`status`	"queued" \| "working" \| "waiting"	no
`message`	string	no	up to 2,000 characters
`assets`	array of string	no	up to 100 items
`requestId`	string	no	A stable id, so a retry does nothing twice · format `^[A-Za-z0-9_.:-]{6,100}$`
`run_id`	string	no	Your run id from the connector's start, so the output ties back to this session · format `^[A-Za-z0-9_.:@-]{1,120}$`

Example

{
  "name": "update_work",
  "arguments": {
    "workId": "workId"
  }
}

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.