Datasets_RelinkTask
const url = 'https://junction-api.qualiastudios.dev/v1/accounts/example/datasets/example:relinkTask';const options = { method: 'POST', headers: {'X-API-Key': '<X-API-Key>', 'Content-Type': 'application/json'}, body: '{"name":"example","validateOnly":true,"maxCost":"example","requestId":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://junction-api.qualiastudios.dev/v1/accounts/example/datasets/example:relinkTask \ --header 'Content-Type: application/json' \ --header 'X-API-Key: <X-API-Key>' \ --data '{ "name": "example", "validateOnly": true, "maxCost": "example", "requestId": "example" }'Moves an upload’s or a merged dataset’s Task link to the Task’s newest published revision, and the links of its takes that name the same Task, then starts the checks a finished preparation starts: the heuristic checks and the graph check, as the caller, capped at max_cost. Publishing a revision relinks nothing and starts no check; this is how a dataset takes it up (Dataset.latest_task_revision above linked_task_revision). validate_only answers what it would relink and the graph run’s credit bound, changing nothing. FAILED_PRECONDITION, in words and with nothing relinked, when nothing is linked or already at the newest revision, when the Task has no published revision, when max_cost is below the bound, or when a heuristic check it would rerun is still running on the dataset. A VLM run on the dataset refuses nothing: the graph run is queued behind it. ABORTED, nothing relinked, when what it read changed before it wrote: a link (another RelinkTask moved it, or UpdateDataset moved the dataset to another Task), the uploads a merged dataset holds, or the Task’s newest revision (one was published since); ask again.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The account id.
The dataset id.
Request Body required
Section titled “Request Body required ”Request for Datasets.RelinkTask.
object
Accounts/{account}/datasets/{dataset}: an upload or a merged dataset.
Relink nothing and start nothing: answer what a call would relink and the credit bound of the runs it would start.
The most the graph run may reserve, in credits. Unset: the bound. Below the bound: FAILED_PRECONDITION, and nothing is relinked. 0 relinks only while no graph run would start: a preview’s credit_bound of 0, confirmed.
A UUID naming this call for the heuristic run’s admission, so a retry starts it once; empty: a new one.
Example generated
{ "name": "example", "validateOnly": true, "maxCost": "example", "requestId": "example"}Responses
Section titled “ Responses ”OK
Response for Datasets.RelinkTask.
object
Accounts/{account}/tasks/{task}: the Task the dataset links.
The Task’s display name, as its newest revision has it.
The revision the dataset’s link carried before; 0 when it was made while the Task was a draft.
The revision it carries now (with validate_only, would carry).
Takes whose own link to the Task moved with it (or would).
Accounts/{account}/checks/{check}/runs/{run}: the runs started, heuristic first; empty with validate_only. The graph run is left out when it has nothing to read (no take with a published video).
The credit bound of the graph run: its estimate, what it may reserve at most. 0 when no graph run starts. Heuristic runs reserve nothing.
Example generated
{ "task": "example", "taskDisplayName": "example", "previousRevision": 1, "revision": 1, "relinkedEpisodeCount": 1, "checkRuns": [ "example" ], "creditBound": "example"}default
Section titled “default ”Default error response
A refusal from the API itself.
object
The gRPC code name in upper case, e.g. NOT_FOUND.
Whether the same call may succeed if retried.
Empty, except when a dataset copy or move is refused: then one google.rpc.ErrorInfo with the refusal’s reason code, its domain and, in metadata, the datasets it names.
object
A refusal from the gateway before the call reaches the API, for example 401 bad or missing API key, 403 key lacks the scope or environment closed, 413 body too large.
object
What went wrong.
Example generated
{ "code": "example", "message": "example", "retryable": true, "details": [ {} ]}