When Custom Errors Vanish: Inngest's Silent Serialization Trap

Developers using Inngest often rely on custom error classes for sophisticated error classification and monitoring, but class identity is silently lost during step serialization—breaking retry logic and error reporting without warning. This creates a critical blind spot in production observability that's difficult to diagnose. Understanding and working around this limitation is essential for anyone building reliable workflows with Inngest.