Skip to content

Job is stuck in provisioning if launch fails #22

Open

Description

@oldsj

I attempted a cloudexec launch but it failed due to there not being an ./input directory present locally.
cloudexec status shows the job provisioning even though a droplet was never created.
image

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions