I'd look at your code honestly, it's been working great for me both in personal and work projects
I'd look at your code honestly, it's been working great for me both in personal and work projects
sentry.captureException and also sometimes when there is an error deep in a library then there is no context
throw new Error and the full stack trace is there
itty-durable is probably losing the context somehow since they use a proxy object or something. this one does get de-duplicated though
, current options seems to all require either R2 or an external destination to store them, with each storing costing a R2 write

)
sentry.captureExceptionthrow new Erroritty-durable