Duplicate a test run

Cloud of execution_region_override (e.g. gcp or aws). Absent means gcp. Ignored without a region override.

Run this test in a named region of execution_cloud_override instead of wherever it would otherwise go, ahead of any execution location pinned on its workspace, account or company. Rejected with a 400 unless that location runs this test's type. A run reaching a customer network over Link stays in the default location unless its workspace is routed over mablnet, and a performance run over Link always stays there.

Target execution test runner image tag to execute

Optional orchestration runtime version to use, if applicable. Otherwise use default orchestration version.

true if the run should record video

Test execution runtime to use

Test Recovery Agent mode. Use inherit (plan-level only) to defer to the workspace-level default.

How much Chrome trace data to capture. full records the complete category set, and is what the "Download step trace" artifact contains. metrics records only the categories the published performance measures are computed from, so a trace downloaded from a metrics run carries the film strip and timeline but not the full set of Chrome records. inherit defers to the next level down.

Whether the Chrome trace file is kept after a run. keep makes it available as the Download step trace artifact. discard publishes the same performance measures when the analysis succeeds; with no file kept there is no fallback, so a failed analysis loses the measure for that step. A run's inherit defers to its plan's setting; a plan's inherit, like no setting at all, means discard.

Override for default debug level of test runs. Higher debug levels include more debug information in the run. Default is zero and runs with standard debugging.

Preview API image to use

Object id. Set by system.

The trigger armed by notify_on_complete. Present only on the response that created this plan run, never stored.

Cloud safe ID representation (e.g. GCP/email/Kubernetes safe)

Object id. Set by system.

The organization that this run belongs to

DEPRECATED - The application that this run is for

DEPRECATED - The environment that this run is against

DEPRECATED - The deployment that this run is for

If true will capture additional debugging information during execution

Current status of the job

Cause for setting given status, such as failure cause. Updated in pairs with Status.

Cloud of execution_region_override. Absent means gcp. Written and stripped exactly like execution_region_override.

Runs every test of this plan run in a named region of execution_cloud_override, ahead of any execution location pinned on the workspace, account or company. Writable only through the global-admin rerun endpoint: it is stripped from plan run update bodies and is not carried over when a plan run is re-run manually, so write scope on plan runs or on integrations cannot choose a location.

Target execution test runner image tag to execute

Optional orchestration runtime version to use, if applicable. Otherwise use default orchestration version.

Preview API image to use

Test Recovery Agent mode. Use inherit (plan-level only) to defer to the workspace-level default.

How much Chrome trace data to capture. full records the complete category set, and is what the "Download step trace" artifact contains. metrics records only the categories the published performance measures are computed from, so a trace downloaded from a metrics run carries the film strip and timeline but not the full set of Chrome records. inherit defers to the next level down.

Whether the Chrome trace file is kept after a run. keep makes it available as the Download step trace artifact. discard publishes the same performance measures when the analysis succeeds; with no file kept there is no fallback, so a failed analysis loses the measure for that step. A run's inherit defers to its plan's setting; a plan's inherit, like no setting at all, means discard.

Where the test lives

Reference id to this plan in another system

Reference id to this plan in another system

[Deprecated] Test execution runner to use, optional

The ID of the user who terminated this plan run

the id of process that scheduled this plan run

the type of trigger scheduling this plan run

the id of the entity that triggered the plan run

the type of the entity that triggered the plan run

this plan run was triggered by a mabl support team member

The source control tag override that was used for this plan run, if any

time the plan run was created

The ID of the user who created this plan run

time the plan run was scheduled

time the plan run completed

time the plan run object was last updated

The ID of the user who last updated this plan run

DEPRECATED - Graph describing how the journey runs in this plan run will execute

Indicates the retry count for this plan run (0 = initial run, 1 = first retry, etc.)

The ID of the plan run that triggered this retry

If this is a retry, whether to retry all tests, failed tests only, or failed and skipped tests

Whether or not the plan will retry