Hi all,
Since this morning (2026-10-19, ~07:34 UTC), about 20% of invocations of our async events consumer fail as UNHANDLED_EXCEPTION in the developer console metrics. That keeps tripping the “Invocation success rate” alert. Nothing changed on our side: the same code ran from Oct 15 with zero errors.
Setup:
- Web trigger pushes Linear webhook events to a queue (
queue.pushwithconcurrency: { key, limit: 1 }), and aconsumermodule processes them (timeoutSeconds 120) - App ID: ec111fc8-df5d-4a5f-b0cc-d5eba3b2959d, production environment
What we see:
- Only the consumer function errors. The web trigger, product event triggers and resolver are all clean.
- The failing invocations write nothing to the app logs. No error, no stack.
- Every event we pushed is still processed exactly once and logged normally. Nothing comes back with a retryContext, so we’re not losing data.
- We deployed a version that wraps the entire consumer handler in try/catch and logs any throw. The catch never fires, and the error rate is unchanged (~22% over the last 3 hours).
- We also checked the whole codebase for floating promises (typescript-eslint no-floating-promises): zero.
- Possibly related: three
forge deployruns this morning failed at “Deploying to environment” with a generic “Deployment failed” and succeeded on a plain re-run.
So it looks like the exception is raised outside our handler, in the runtime or queue layer.
Is anyone else seeing this on their queue consumers today? And could someone from Atlassian take a look? We’ve opened a support ticket too: Jira Service Management
Thanks!