Datasets_ListReingestNotCarried
const url = 'https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/reingests/example/notCarried';const options = {method: 'GET', headers: {'X-API-Key': '<X-API-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/reingests/example/notCarried \ --header 'X-API-Key: <X-API-Key>'Exact durable losses of a successfully published re-cut, in old take number order. FAILED_PRECONDITION until an authenticated result exists. This read never dispatches, retries or publishes work.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The account id.
The dataset id.
The reingest id.
Query Parameters
Section titled “Query Parameters ”Defaults to 100; maximum 1000.
A signed continuation from the previous page of this exact result.
Responses
Section titled “ Responses ”OK
One page of old takes whose state the finalized re-cut did not carry. (— api-linter: core::0158::response-plural-first-field=disabled aip.dev/not-precedent: not_carried is a collective result name. —) (— api-linter: core::0132::response-unknown-fields=disabled aip.dev/not-precedent: not_carried names the result and the immutable publication commit binds every page, including an empty zero-loss result, to the same verified publication. —)
object
Old original takes, ordered by their recorded episode_index.
Exact state retained only on an old original identity and its audit after a verified re-cut. Counts include affected legacy children of that take.
object
The old immutable original identity, even when absent from current head.
Its recorded, zero-based number. Cut identities are never listed here.
Why this old take is included in the result.
Person keeps retained on the old identities/audit, not reassigned.
Person rejects retained on the old identities/audit, not reassigned.
Issues raised by people and retained on the old identities/audit.
Notes written by people and retained on the old identities/audit.
Reach records retained on the old identities/audit.
Saved drafts retained on the old identities/audit.
Applied original edits reset by verified re-cut authority, at most one.
Applied original trims reset; a subset of applied_edits.
Legacy split pieces removed from current head but retained on their audit.
Signed continuation; empty only when this complete result ends.
Exact number of old original takes across all pages of this result.
Immutable publication commit; identical on every page.
Example
{ "notCarried": [ { "reason": "REASON_UNSPECIFIED" } ]}default
Section titled “default ”Default error response
The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.
object
The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].
A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.
A list of messages that carry the error details. There is a common set of message types for APIs to use.
Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.
object
The type of the serialized message.
Example generated
{ "code": 1, "message": "example", "details": [ { "@type": "example" } ]}