Interface InstanceGetResponse

The application ID

The optional application specification. For Applications this is returned verbatim. For Jobs additional material will be found.

The type of Application, which can be a job or an application

The application version

True if the instance is archived (protected from automatic deletion)

The code obtained from the Account Server

The accumulated coins accrued by the running Job. Coins are calculated based on the cost multiplied by the launch_exchange_rate. This is a string representation of a Decimal value, e.g. '16.4'

Where available, this is the number of hours that the JOb would take if the collateral Pods had access to only one CPU core. Collateral Pods are all the pods created by the Job that are in addition to the main (controlling) Pod. A value of '0.5' implies the job would have run in 30 minutes on 1 core. The minimum time resolution is 0.001 (3.6 seconds).

Where available, the number of collateral Pods spawned by the instance, typically used by Job instances. Collateral Pods are all the pods created by the Job that are in addition to the main (controlling) Pod. For NEXTFLOW jobs this is a count of the number of Task pods spawned.

The accumulated cost accrued by the running Job. Depending on the the Job, this is either known when the Job completes or may change as the Job runs. This is a string representation of a Decimal value, e.g. '32.8'

An optional error message, used to report underlying problems.

Set if the instance output file permissions are expected to be fixed by the Data Manager when the Instance completes.

Set if the instance has a valid callback token. Instances with a valid token allow users to read files form the project without authentication

If the instance relates to a job, this will be the job collection, as defined in the original collection's job definition.

The Job definition's unique ID

The Job container image type. Typically a single-container 'SIMPLE' (where only one container runs) or a workflow where multiple container images can be spawned (like NEXTFLOW)

If the instance relates to a job, this will be the job, as defined in the original collection's job definition.

If the instance relates to a job, this will be the job's name, as defined in the original collection's job definition.

If the instance relates to a job, this will be the job's name, as defined in the original collection's job definition.

The cost exchange rate that applies to the Job at the time of launch. This is a string representation of a Decimal, e.g. '0.5'

The date and time the instance was started, an ISO-8601 format string.

The application name

The JSON string representation of the JobDefinition's outputs

The application owner, the person who launched the application and is the only user than can stop it.

The phase of the application. This is a string, one of a limited number of values that are defined internally within the Data Manager. The initial phase, indicating that the Instance is preparing to run, is PENDING. The instance is running when the phase is RUNNING. COMPLETED indicates the Instance has finished successfully and FAILED when it's finished but unsuccessfully.

The Project the Instance is running in

The time the instance has spent running in the cluster. It's a string representation of a Python timedelta object, e.g. 0:12:32 for a run-time of 12 minutes and 32 seconds. The run-time must be considered as an estimate until the instance has stopped and the instance is only considered to be running once started has been set.

The date and time the instance started running in the cluster. This is typically close to the launch time but contention may mean the instance starts only when resources are available.

The date and time the instance stopped, an ISO-8601 format string.

A list of Tasks related to the application. Tasks are responsible for creating and deleting the instance. You should fins at least one, assuming the corresponding task has not been deleted.

The application endpoint

A list of Project-relative annotation files.