Skip to main content

​
Deployment states

A launch creates a deployment ID before the environment is ready. getStatus() returns one of three states: The word complete describes deployment readiness. It does not describe learner completion.

​
Wait for readiness

The default interval is five seconds. The default deadline is 15 minutes, checked between status requests. A pending status request is not canceled by the wait deadline or signal. It can still return readiness after either occurs. Cancellation stops later polls and the sleep between polls. It does not end the environment. Provisioning duration depends on the lab. The polling reference explains request timeouts and cancellation.

​
Expiration

A lab has a timeLimit in minutes. Your organization can customize that value within its permitted range. Cybr ends the environment at its deadline. A browser countdown does not control that deadline. The public status response does not supply an authoritative expiration timestamp. A timer based on observed readiness is an estimate. Before telling a learner that an environment remains active, read its current status.

​
End a lab

The request starts teardown. Ending the lab does not record learner completion. If the request returns conflict, read the status before another end request. Do not retry in a tight loop.

​
Deployment runs

Runs describe the individual build and teardown operations:
Each run has an action, status, exitCode, outputs, error, and timestamps. These fields help with diagnostics. Run output can contain secrets. Keep it out of public logs. See launching labs for learner-facing output handling.