Databricks SDK for JavaScript
    Preparing search index...

    Variable WorkspaceStatusConst

    WorkspaceStatus: {
        BANNED: "BANNED";
        CANCELLING: "CANCELLING";
        FAILED: "FAILED";
        NOT_PROVISIONED: "NOT_PROVISIONED";
        PROVISIONING: "PROVISIONING";
        RUNNING: "RUNNING";
    } = ...

    The different statuses of a workspace. The following represents the current set of valid transitions from status to status: NOT_PROVISIONED -> PROVISIONING -> CANCELLED PROVISIONING -> RUNNING -> FAILED -> CANCELLED (note that this transition is disallowed in the MultiWorkspace Project) RUNNING -> PROVISIONING -> BANNED -> CANCELLED FAILED -> PROVISIONING -> CANCELLED BANNED -> RUNNING -> CANCELLED Note that a transition from any state to itself is also valid.

    Type Declaration

    • ReadonlyBANNED: "BANNED"

      Status for banned workspaces. This is intended for use with CE workspaces, although there is no code to enforce this restriction. These workspaces can be unbanned at a later time.

    • ReadonlyCANCELLING: "CANCELLING"

      Status for cancelling workspaces. This state always comes before the CANCELLED status.

    • ReadonlyFAILED: "FAILED"

      Status for workspaces that have failed to be provisioned. This is currently an AWS-only state since an Azure customer can easily retry to launch a workspace that failed to launch, whereas this process is different in AWS.

    • ReadonlyNOT_PROVISIONED: "NOT_PROVISIONED"

      Status for workspaces that have been created but not provisioned yet. It is technically possible for an Azure workspace to be in this state, but only for less than a second in almost all cases, as it will almost immediately transition to PROVISIONING. AWS workspaces may be in NOT_PROVISIONED state for much longer.

    • ReadonlyPROVISIONING: "PROVISIONING"

      Status for workspaces being provisioned.

    • ReadonlyRUNNING: "RUNNING"

      Status for running workspaces.