app resume

writesrepeatable--dry-run

Starts a paused application again, at the instance count and size it was paused with. There is nothing to rebuild or redeploy: the deployment that was already there is what comes back.

Usage

outplane app resume [APP]

Arguments

Argument	Type	Description
`APP`	`string`	App name or id. Defaults to the linked app.

Output

Field	Type	Description
`app`	`string`
`appId`	`string`
`paused`	`bool`	The state the application is now in.
`instances`	`int`	The configured count, which pausing does not change.
`changed`	`bool`	False when it was already in that state.

Examples

See what it would do, without doing it

outplane app resume --dry-run

Resume an application

outplane app resume checkout

Resume the linked one and read the result

outplane app resume --json --fields paused,changed

{
  "changed": true,
  "paused": false
}

What to Know

Idempotent. Pausing something already paused changes nothing, reports changed false, and exits 0.
Applied immediately, without a deployment.
The configured replica count is kept, so resuming returns to the scale that was set rather than to a single instance.
A paused application still reports its last deployment's state in deploymentStatus. status is what says paused.

Errors

Beyond 0 for success, this command exits with:

Exit	Kind	Meaning
`2`	`usage`	Invalid arguments, unknown flag, or client-side validation failure.
`3`	`auth`	Not authenticated, token revoked or expired, or forbidden for this team.
`5`	`not_found`	The named resource does not exist, or is not visible to this credential.
`8`	`upstream`	The Out Plane API returned a server error.