Workspace Still Has Services
workspace-has-services · 409
The workspace still owns services, so the API didn't delete it.
All pages
Deleting a workspace never takes its services down with it. serviceNames lists them by name, and serviceCount counts them. Once the services are gone, a workspace that still owns buckets is refused the same way, as workspace-has-buckets.
Besides the members every error carries, this type adds workspaceId, serviceCount and serviceNames.
- A service in one of the workspace's projects is still there, whether it runs, sleeps or is stopped.
- Ask the user before deleting any service: their data goes with it.
- Delete each with
ghaym cloud services delete <service> --env <env> --apply, then its buckets, then delete the workspace again.
json
{
"type": "workspace-has-services",
"title": "Workspace Still Has Services",
"detail": "This workspace still owns 2 service(s) — orders-db, storefront. Destroy them first, then delete the workspace.",
"workspaceId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
"serviceCount": 2,
"serviceNames": [
"orders-db",
"storefront"
],
"requestId": "req-1785231000000-4f7b2c9ae",
"timestamp": "2026-07-28T09:30:00.000Z",
"path": "/v1/workspaces/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
"method": "DELETE",
"instance": "DELETE /v1/workspaces/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
"status": 409,
"docs": "https://ghaym.me/docs/errors/workspace-has-services"
}