finish_submission
Finish submission. Finish an upload: ready (with the pieces you published from it) or failed (with why).
Where it is
In the drops area (upload links, people's uploads and share links): open it with tools_for { area: "drops" }, then call it with use_tool { name: "finish_submission", 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: closes the lease.
Inputs
| Input | Type | Needed | About |
|---|---|---|---|
subId | string | yes | The upload's id from list_submissions · format `^[a-f0-9]{24}$` |
lease | string | yes | The lease claim_submission gave you · format `^[a-f0-9]{32}$` |
status | "ready" | "failed" | yes | |
assets | array of string | no | up to 100 items |
message | string | no | up to 2,000 characters |
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": "finish_submission",
"arguments": {
"subId": "subId",
"lease": "lease",
"status": "ready"
}
}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.