`studio_status`

See a studio job. A studio job's progress (render or sound_render from studio_job). When it is done, give title (the human name, e.g. "Spring reel · v2"): the result goes into the company's media library for the owner to review (never public). A big film can answer status "uploading": call studio_status again with the same job_id and title in 30-60 s (it carries on with the same upload). A file whose sounds lack a known licence is refused, plainly. To post it afterwards, propose the post: that waits for the owner's yes.

Where it is

In the studio area (making films and sound in the cloud studio (Video Desk, Immersive Desk)): open it with tools_for { area: "studio" }, then call it with use_tool { name: "studio_status", 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: files a finished render in the company's own media library as a draft for the owner's review, never public.

Inputs

Input	Type	Needed	About
`project`	string	yes	format `^[a-z0-9][a-z0-9._-]{0,63}$`
`job_id`	string	yes	up to 80 characters
`title`	string	no	When done: the human name in the media library. · 3 to 120 characters
`run_id`	string	yes	The run_id from start. Pass it on every call: it keeps your task held. · 1 to 100 characters

Example

{
  "name": "studio_status",
  "arguments": {
    "project": "project",
    "job_id": "job id",
    "run_id": "the run_id from start"
  }
}

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.