Skip to main content

Error Handling & Debugging

Defensive coding in iXML is essential because services usually handle untrusted input, communicate with external dependencies, and orchestrate database side effects that can fail at any point. Without proper error handling, a single malformed JSON payload or a database constraint violation can crash an entire service, returning raw internal error messages to the client and leaving data in an inconsistent state.

iXML provides a structured error handling mechanism through the TRY construct and explicit error/warning commands, combined with a debug namespace for development-time inspection. This section covers the full error handling and debugging toolkit.

Sub-chapters​

  • Try / Catch — The try/catch/else/finally construct, execution flow, and practical examples
  • Throwing Errors — The error and warning commands for explicitly raising exceptions
  • API Error Patterns — Stable response envelopes, HTTP status codes, and implementation patterns for ZeyOS API services
  • Debugging & Troubleshooting — Parser errors, runtime errors, debug commands, and systematic debugging strategies
  • Best Practices — Guidelines and common mistakes for robust error handling