Workspace Not Found

workspace-not-found · 404

The workspace the call named isn't one the caller belongs to, so nothing ran.

Here resourceId repeats the workspace id the call sent. A workspace that doesn't exist, one the caller isn't a member of, and a deleted one all answer this same 404.

Besides the members every error carries, this type adds resourceType and resourceId.

Common causes

  • The value isn't a workspace id: a name sent where the id goes.
  • The caller isn't a member of that workspace, or was removed from it.
  • The workspace was deleted.

How to fix the call

  • Read resourceId and compare it with the value you meant to send.
  • List the caller's workspaces with ghaym cloud workspaces list and send one of those ids.
  • Don't retry unchanged: the same call answers the same 404 for as long as nothing changes.

Example response

json
{
  "type": "workspace-not-found",
  "title": "Workspace Not Found",
  "detail": "Workspace with ID '0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401' was not found",
  "resourceType": "Workspace",
  "resourceId": "0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects",
  "method": "GET",
  "instance": "GET /v1/projects",
  "status": 404,
  "docs": "https://ghaym.me/docs/errors/workspace-not-found"
}