Missing resources, wrong scope, lifecycle drift, and state mismatches.
Last reviewed: March 4, 2026|55 mapped errors|Page 4 of 4
Resource-state errors appear when identifiers, region or account scope, lifecycle state, or consistency timing do not match request assumptions.
Provider-specific error pages mapped to this category (55 total). Showing 46-55.
HTTP 301 Moved Permanently means the resource has a new permanent URI and future requests should use it.
HTTP 302 Found means the resource is temporarily at a different URI and clients should follow Location for now.
HTTP 303 See Other means the server directs the client to retrieve another resource, usually with GET.
HTTP 304 Not Modified means conditional request found that the cached representation is still valid.
HTTP 305 Use Proxy is deprecated and should not be generated in modern HTTP systems.
HTTP 307 Temporary Redirect means the resource is temporarily elsewhere and request method must be preserved.
HTTP 308 Permanent Redirect means resource moved permanently and redirect must preserve request method and body.
HTTP 404 Not Found means the origin server did not find a current representation for the target URI.
HTTP 410 Gone means the target resource is no longer available at this URI and is expected to be permanently removed.
HTTP 423 Locked means the source or destination resource is locked and cannot be modified yet.
Compare Guide
Use 403 for explicit access denial, or 404 to conceal resource existence when security policy requires reducing endpoint and object enumeration risk.
Compare Guide
Learn when to return 404 (missing or temporary absence) versus 410 (intentional permanent removal), including redirect and cache implications.
Playbook
Use this playbook to separate temporary missing-resource lookups from permanent removals, then fix scope, lifecycle, and identifier drift safely.
Temporary 404s often resolve after propagation or deployment completion, while permanent removals are typically explicit lifecycle events (for example 410 semantics).
Many control planes are eventually consistent. Read-after-write visibility can lag and briefly return not-found responses.
Confirm exact scope and identifier tuple: resource name, region, account/subscription/project, and parent container.