Missing resources, wrong scope, lifecycle drift, and state mismatches.
Last reviewed: February 13, 2026|52 mapped errors|Page 3 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 (52 total). Showing 31-45.
Azure returns `VMExtensionNotFound` when a VM operation references an extension resource name that does not exist on the target VM.
Azure returns `VMNetworkInterfaceNotFound` when a VM operation references a network interface that cannot be resolved in the current scope.
Azure returns `VMSSInstanceNotFound` when a requested scale set VM instance ID cannot be resolved in the target scale set context.
GCP ALREADY_EXISTS means a create call attempted to use a resource identity that is already present in the target namespace.
GCP BILLING_DISABLED means the consumer project has no active billing account attached or its linked billing account is not in an active state for service usage.
GCP INVALID_STATE is typically a provider-specific signal that current resource state does not allow the requested action.
GCP NOT_FOUND means the requested entity cannot be resolved in the specified project, location, or parent resource namespace.
GCP OUT_OF_RANGE means input is structurally valid but falls outside current valid bounds for the resource or iterator state.
HTTP 300 Multiple Choices means the target has more than one representation and the client should choose one.
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.
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.