Skip to content

[Bug]: Workspaces stuck indefinitely on "Starting" / Provisioning hang & billing deducts #7

Description

@mutiaraputra

Environment

  • OS: Windows 10 (PowerShell)
  • CLI / Plugin: runcode CLI v0.1.0 (via Claude Code Plugin)
  • Provider / Region: AWS / us-east-1 (and auto-resolved)

Description

Creating new workspaces (both via Web UI and CLI) results in an infinite "Starting" status lock. The provisioning pipeline appears stuck before the container / SSH daemon becomes ready, causing compute billing to deduct balance even though the instance is completely inaccessible.

Steps to Reproduce

  1. Run runcode create --size tiny --region us-east-1 --force (or create via Web Dashboard).
  2. The CLI hangs on provisioning until it hits the timeout.
  3. Check runcode list: the status is locked in starting stopped.
  4. Web UI options are restricted (only "Rename" is available).
  5. Attempting to stop transitions to stopping stopped indefinitely until forcefully deleted with runcode delete <ws> --yes.

Expected Behavior

Workspace should boot up within seconds and become accessible via SSH/Web IDE.

Actual Behavior

  • Workspace stays stuck on starting indefinitely.
  • Balance is deducted for running time while the workspace is stuck in the provisioning loop.
  • Affected Workspace IDs (now deleted): #68781, #68782, #68783.

Additional Context

  • hello@runcode.io email address bounces (mailbox unavailable).
  • Account balance is active and positive ($2.00 initial credit).

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