error-handling

Error handling in Wasp applications enforces a standardized HTTP error sequence (401 → 404 → 403 → 400 → 500) using HttpError from wasp/server on the backend, Zod for input validation, and user-friendly error messages on the client side with retry logic in React components.

Zod provides type-safe input validation for Wasp backends, catching invalid data before it reaches your operations. Pair Zod schemas with HttpError to throw appropriate 400 errors when validation fails, preventing bad data and improving application robustness.

Use HttpError from wasp/server to throw specific status codes in the correct sequence: 401 for unauthenticated requests, 404 for not found, 403 for forbidden, 400 for invalid input, and 500 for server errors. This ensures consistent, secure error responses across all operations.

Yes. Catch HTTP errors from server operations in React components and display toast notifications or user-friendly messages instead of raw errors. Implement retry logic for transient failures to improve client-side resilience and user experience.

While Zod is the recommended approach for type-safe input validation in Wasp, you can implement basic error handling with HttpError alone. However, Zod integrates seamlessly and provides comprehensive validation that prevents invalid data from reaching your backend operations.

The error sequence (401 → 404 → 403 → 400 → 500) prioritizes authentication and authorization checks before validation, ensuring security vulnerabilities aren't exposed and errors are thrown in the correct logical order for reliable error handling.