Your workspace is currently in an INACTIVE state, which is likely why your deployment is stuck in QUEUED and a previous deployment may have been removed. We experienced a major service disruption earlier today that has since been resolved, but there may be lingering effects on newly created workspaces. Please try logging out and back in, then trigger a fresh redeploy from your service's deployments page - if the workspace state doesn't recover, let us know.