ask_owner
Ask owner. Say an edit needs the owner's answer: the collage (the plan in pictures) or the final.
Where it is
In the edits area (edits, looks, formats, music, scores and the owner's notes on media): open it with tools_for { area: "edits" }, then call it with use_tool { name: "ask_owner", 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 question to the owner.
Inputs
| Input | Type | Needed | About |
|---|---|---|---|
editId | string | yes | The edit id (its upload id) · format `^[a-f0-9]{24}$` |
stage | "collage" | "final" | yes | |
what | string | yes | What the owner is asked, in one plain sentence · 1 to 500 characters |
version | string | no | up to 40 characters |
assetId | string | no | The piece the answer is about (the collage pictures or the final film), shown on the owner's card. Default: the edit's newest part of that stage. · format `^[a-z0-9][a-z0-9-]{0,159}$` |
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": "ask_owner",
"arguments": {
"editId": "editId",
"stage": "collage",
"what": "The invoice PDF did not open"
}
}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.