Is it possible source map a handled exception stack trace from a tail worker?
Is it possible source map an exception stack trace from a tail worker when the exception is not an unhandled exception?
We have use cases where we need to handle exceptions from the perspective of the originating worker (i.e. we have batch requests where parts can fail, but we want to handle them and complete the overall requests). In those cases, we log the exceptions to a tail worker via a diagnostic channel, but we don't get mapped stack traces which makes them difficult to debug. I'd love to be able to explicitly map those stack traces from a tail worker.
0 Replies