@jdkealy Pedestal wraps all exceptions thrown by interceptors in an ExceptionInfo. You can either get the cause off the thrown ExceptionInfo pull it out of the ex-data using the :exception key. The joining of interceptor name and original message is not configurable. For additional attrs in ex-data, see http://pedestal.io/reference/error-handling

Hey. I also have a question about exceptions. In a ‘normal’ synchronous interceptor I can just raise (or not catch) exceptions, and they’ll eventually end up in an :error interceptor. However, I can’t figure out what to do with exceptions occuring in asynchonous interceptors. The docs say they should return channels with context maps, and that exceptions are put in ::chain/error in the context map wrapped in an ExceptionInfo, but I am struggling to find out how to create such a wrapped exception to put in the context in my asynchronous interceptor.