d0fc0114da66
Update Run Policy
Used to update existing run Policies
Path parameters
The ID of the Run Policy to update
Headers
If-Match header according to http/1.1 spec section 14.24
Request body
Plan id. Set by system.
Cloud safe ID representation (e.g. GCP/email/Kubernetes safe)
DEPRECATED - use workspace_id instead
The workspace id this plan belongs to
The type of plan
Where the test lives
Reference id to this plan in another system
DEPRECATED - use deployment_ids - The deployment ID associated with this run policy
The deployment IDs associated with this run policy
DEPRECATED - Alias for web_url
Optional URL override for web deployments
Optional URL override for API deployments
DEPRECATED - use link_agent_labels
Optional Link Agent Labels override for the deployment
Optional link_bypass_mabl_proxy override for the deployment (mabl link only)
Route this run's test traffic through the triggering user's own personal mablnet Link tunnels, in addition to the environment's configured link agents. Overrides the deployment's use_personal_link_agent for this run. The owner is the user who triggers the run, resolved server-side — there is no id to pass. By default the run stripes across every live personal tunnel the user has (e.g. one per machine); set personal_link_tunnel_label to pin it to one. mablnet-only; requires that user to have at least one live personal Link Agent connected.
Restrict use_personal_link_agent to a single personal tunnel by its (server-derived) Link label, instead of striping across all of the user's live personal tunnels. Ignored when use_personal_link_agent is not set.
Optional ID of the credentials object to use with this run policy
Flag indicating whether or not credentials are required for this run policy
Optional ID of credentials to pass in the HTTP request (as opposed to interactive login credentials)
Flag indicating whether or not HTTP auth credentials are required for this run policy
Flag indicating whether or not custom HTTP headers are required for this run policy
Whether this run policy is currently enabled
Whether this run policy was automatically generated by the platform as opposed to being entered by a user
Whether this is the default run policy
Whether this is an ephemeral run policy created for an ad hoc plan run
time the run policy was created
The ID of the user who created this run policy
time the run policy object was last updated
The ID of the user who last updated this run policy
The display name of the run policy
Detailed description of this run policy
Server-maintained denormalized list of invariant ids of every test referenced anywhere in this plan's execution_stages. Used to index plan-by-test lookups in Datastore (which cannot index doubly-nested array paths). Do not set from clients - any value provided will be overwritten on save.
The amount of time to wait after page loads, if supported by the runtime.
Any specific flow variants that should be used when running the plan. Any flow variants set here will be used instead of the head version when the given flow is encountered for this plan
DEPRECATED - The browser that should be used when executing journeys, use browser_types
The browser that should be used when executing journeys
Devices to use for mobile testing
Desktop (default) or mobile device emulation. When mobile is specified, browser_types is ignored in favor of web_emulation_types.
[Deprecated] Test execution runner to use, optional
Override the Node.js execution runtime variant, if v2 runtime in use
if > 1, will start multiple copies of each journey run when this plan runs
The debugging level to use for the test run. Higher debug levels include more debug information in the run. Default is zero and runs with standard debugging.
Exclude action attributes during execution
Exclude specific observers during execution
If true, runs of this plan will automatically be retried if any journey run fails
If true, will only retry journeys that had failed journey runs
If true, use and maintain models for visual change detection
Controls whether or not the x-mabl-agent header is sent on requests (can be overridden by test)
available runner sizes
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.
Optional map of mobile platform => mobile app file ID override
Response
The updated run policy
Plan id. Set by system.
Cloud safe ID representation (e.g. GCP/email/Kubernetes safe)
DEPRECATED - use workspace_id instead
The workspace id this plan belongs to
The type of plan
Where the test lives
Reference id to this plan in another system
DEPRECATED - use deployment_ids - The deployment ID associated with this run policy
The deployment IDs associated with this run policy
DEPRECATED - Alias for web_url
Optional URL override for web deployments
Optional URL override for API deployments
DEPRECATED - use link_agent_labels
Optional Link Agent Labels override for the deployment
Optional link_bypass_mabl_proxy override for the deployment (mabl link only)
Route this run's test traffic through the triggering user's own personal mablnet Link tunnels, in addition to the environment's configured link agents. Overrides the deployment's use_personal_link_agent for this run. The owner is the user who triggers the run, resolved server-side — there is no id to pass. By default the run stripes across every live personal tunnel the user has (e.g. one per machine); set personal_link_tunnel_label to pin it to one. mablnet-only; requires that user to have at least one live personal Link Agent connected.
Restrict use_personal_link_agent to a single personal tunnel by its (server-derived) Link label, instead of striping across all of the user's live personal tunnels. Ignored when use_personal_link_agent is not set.
Optional ID of the credentials object to use with this run policy
Flag indicating whether or not credentials are required for this run policy
Optional ID of credentials to pass in the HTTP request (as opposed to interactive login credentials)
Flag indicating whether or not HTTP auth credentials are required for this run policy
Flag indicating whether or not custom HTTP headers are required for this run policy
Whether this run policy is currently enabled
Whether this run policy was automatically generated by the platform as opposed to being entered by a user
Whether this is the default run policy
Whether this is an ephemeral run policy created for an ad hoc plan run
time the run policy was created
The ID of the user who created this run policy
time the run policy object was last updated
The ID of the user who last updated this run policy
The display name of the run policy
Detailed description of this run policy
Server-maintained denormalized list of invariant ids of every test referenced anywhere in this plan's execution_stages. Used to index plan-by-test lookups in Datastore (which cannot index doubly-nested array paths). Do not set from clients - any value provided will be overwritten on save.
The amount of time to wait after page loads, if supported by the runtime.
Any specific flow variants that should be used when running the plan. Any flow variants set here will be used instead of the head version when the given flow is encountered for this plan
DEPRECATED - The browser that should be used when executing journeys, use browser_types
The browser that should be used when executing journeys
Devices to use for mobile testing
Desktop (default) or mobile device emulation. When mobile is specified, browser_types is ignored in favor of web_emulation_types.
[Deprecated] Test execution runner to use, optional
Override the Node.js execution runtime variant, if v2 runtime in use
if > 1, will start multiple copies of each journey run when this plan runs
The debugging level to use for the test run. Higher debug levels include more debug information in the run. Default is zero and runs with standard debugging.
Exclude action attributes during execution
Exclude specific observers during execution
If true, runs of this plan will automatically be retried if any journey run fails
If true, will only retry journeys that had failed journey runs
If true, use and maintain models for visual change detection
Controls whether or not the x-mabl-agent header is sent on requests (can be overridden by test)
available runner sizes
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.
Optional map of mobile platform => mobile app file ID override