Error Codes Reference

Cloud Factory uses a standardized error handling system based on RFC 7807 Problem Details. All error responses are returned with Content-Type: application/problem+json.

Error Response Format

{
  "type": "https://api.t-2.cloud/problems/entity-not-found",
  "title": "Entity Not Found",
  "status": 404,
  "detail": "Order not found: 123e4567-e89b-12d3-a456-426614174000",
  "instance": "/orders/123e4567-e89b-12d3-a456-426614174000",
  "code": "ENTITY_NOT_FOUND",
  "timestamp": "2026-03-15T10:30:00.000Z",
  "correlationId": "req-abc-123",
  "entityType": "Order",
  "entityId": "123e4567-e89b-12d3-a456-426614174000"
}

Standard Fields

Additional fields from the error's details object are spread into the response body.

Error Codes by Category

Validation Errors (HTTP 400)

Validation Error with Field Details

{
  "type": "https://api.t-2.cloud/problems/validation-error",
  "title": "Validation Error",
  "status": 400,
  "detail": "Validation failed",
  "fieldErrors": [
    {
      "field": "email",
      "code": "isEmail",
      "message": "email must be a valid email address"
    }
  ]
}

class-validator Errors

When NestJS class-validator pipe rejects input, errors are returned as:

{
  "type": "https://api.t-2.cloud/problems/http-400",
  "title": "Bad Request",
  "status": 400,
  "detail": "email must be an email; firstName should not be empty",
  "errors": ["email must be an email", "firstName should not be empty"]
}

Authentication Errors (HTTP 401)

Authorization Errors (HTTP 403)

Not Found Errors (HTTP 404)

Conflict Errors (HTTP 409)

Rate Limiting Errors (HTTP 429)

Server Errors (HTTP 500/502/503)

Domain-Specific Errors

Domain-specific errors use dynamic codes set at instantiation (e.g., ORDER_ITEM_NOT_FOUND, PROVISIONING_TIMEOUT).

Error Class Hierarchy

Error
  └── DomainError (abstract)
        ├── ValidationError (400)
        ├── InvalidInputError (400)
        ├── InvalidStateTransitionError (400)
        ├── AuthenticationError (401)
        │   ├── InvalidCredentialsError
        │   ├── TokenExpiredError
        │   └── InvalidTokenError
        ├── AuthorizationError (403)
        │   ├── InsufficientPermissionsError
        │   ├── TenantAccessDeniedError
        │   └── ResourceAccessDeniedError
        ├── NotFoundError (404)
        │   └── EntityNotFoundError
        ├── ConflictError (409)
        │   ├── DuplicateEntityError
        │   ├── ConcurrencyError
        │   └── BusinessRuleViolationError
        ├── RateLimitExceededError (429)
        ├── QuotaExceededError (429)
        ├── InternalError (500)
        ├── IntegrationError (502)
        ├── ServiceUnavailableError (503)
        ├── OrderError (400)
        ├── ProvisioningError (500)
        ├── BillingIntegrationError (502)
        ├── NotificationError (500)
        └── SupportTicketError (400)

Fallback Behavior

When an error does not match a known DomainError code, the filter falls back to HTTP status-based problem types:

Unhandled exceptions (non-DomainError, non-HttpException) always return:

{
  "type": "https://api.t-2.cloud/problems/http-500",
  "title": "Internal Server Error",
  "status": 500,
  "detail": "Internal server error"
}

Stack traces and internal details are never leaked to the client.

Source Files

• Error classes: packages/common/src/errors/domain.errors.ts
• Problem types: packages/common/src/errors/problem-types.ts
• Exception filter: packages/common/src/infrastructure/filters/http-exception.filter.ts