Inspect And Operate

Errors

Cessy errors should tell you which layer failed: auth, permission, validation, command logic, projection read, policy execution, webhook handling, adapter call, or platform operation.

Common statuses

StatusMeaning
400Invalid request shape, invalid query, or failed validation.
401Missing or invalid authentication.
403Authenticated caller lacks required scope, role, attribute, or app access.
404Tenant, app, environment, command, projection, or resource not found.
409Business conflict, concurrency conflict, duplicate handling, or invalid state transition.
422Semantically invalid command or payload.
500Unexpected platform or integration failure.

Command failures

Command failures usually mean the business decision was rejected. Inspect:

  • command input
  • actor and permissions
  • loaded decision state
  • validation error
  • emitted or missing events

Policy and adapter failures

Policy failures happen after an event or trigger. Check Activity for the triggering event, policy run, adapter call, retry behavior, and final error.

Webhook failures

Webhook failures often come from auth, payload shape, guard expressions, mapping, or downstream command validation. Keep sender request ids in logs when possible.

Troubleshooting order

  1. Confirm tenant, app, and environment.
  2. Confirm auth and scopes.
  3. Check permissions for the actor.
  4. Validate request shape against generated contract.
  5. Inspect Activity for command, event, policy, webhook, and adapter traces.
  6. Check Data Explorer for projection state.
  7. Inspect error logs for platform-level failures.