Skip to content
Qualia Docs

Datasets_GetReingest

GET
/v1/accounts/{account}/datasets/{dataset}/reingests/{reingest}
 
curl --request GET \
  --url https://dev-api.qualiastudios.dev/v1/accounts/example/datasets/example/reingests/example \
  --header 'X-API-Key: <X-API-Key>'

Where a re-ingest has got to, from durable state. It never retries or cancels the work. One step it does take: a re-ingest whose ingest committed while the server coordinating it was replaced is published by the read that finds it.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
account
required
string

The account id.

dataset
required
string

The dataset id.

reingest
required
string

The reingest id.

Responses

Section titled “ Responses ”

200

Section titled “200 ”

OK

Media type application/json

One re-ingest of an upload under a new meta/ingest.toml (Datasets.ReingestDataset).

object
name

Accounts/{account}/datasets/{dataset}/reingests/{reingest}

string
state

Where the work stands.

string format: enum
Allowed values: STATE_UNSPECIFIED QUEUED PREPARING PUBLISHING SUCCEEDED FAILED
unchanged

The posted config was the published one: nothing ran, and this names the publication that already carries it.

boolean
failureReason

Why it failed; empty unless FAILED.

string
progress

While PREPARING: the live step, the same open set of fields the upload feed reports (step, detail, counters).

object
episodeCount

Once SUCCEEDED: episodes in the published generation.

string
frameCount

Once SUCCEEDED: frames in the published generation.

string
poseAttempt

Attempt currently preparing a pose move, or zero when cancellation is unavailable.

integer format: int32
publicationFailure

Most recent safe publication failure while publishing, if any.

string
recutResult

Present only when a verified re-cut result committed atomically with this successful publication. Absence is not an empty/clean result.

object
notCarriedCount

Exact number of old original takes with state not carried. Zero means the verified publication lost no state; no such take is listed.

string
publicationCommit

Immutable publication commit, used to bind every page of the result.

string
Example 
{
  "state": "STATE_UNSPECIFIED"
}

default

Section titled “default ”

Default error response

Media type application/json

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
code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32
message

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.

string
details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object
@type

The type of the serialized message.

string
key
additional properties
any
Example generated
{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}