Repository navigation
Cloudflare queues #14387
Description
Activity
- moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3
on Nov 21, 2024 This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you remove the label
Waiting for: Community, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
As for workarounds, could you please provide a minimal reproduction repo?
index.ts:... const app = new Hono<Environment>(); ... const handler = Sentry.withSentry((env: CloudflareBindings) => { const { id: versionId } = env.CF_VERSION_METADATA; return { // https://docs.sentry.io/platforms/javascript/guides/cloudflare/configuration/options/#core-options dsn: env.SENTRY_DSN, release: versionId, environment: process.env.NODE_ENV, attachStacktrace: true, sendDefaultPii: true, _experiments: { enableLogs: true }, tracesSampleRate: 1.0, profilesSampleRate: 1.0, }; }, { fetch: app.fetch, queue, }); export default handler satisfies ExportedHandler< CloudflareBindings, LifecycleEventMessage >;
queue/index.ts:... const queue: ExportedHandlerQueueHandler< CloudflareBindings, LifecycleEventMessage > = async (batch, env): Promise<void> => { console.log(`Processing batch from queue: ${batch.queue}`); switch (batch.queue) { ...[do some processing based on what queue the message is in] } }; export default queue;
1 remaining item
- moved this from Waiting for: Community to Waiting for: Product Owner in GitHub Issues with 👀 3
on Feb 26, 2026 - moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3
on Feb 26, 2026 - added a commit that references this issue
on Apr 27, 2026 A PR closing this issue has just been released 🚀
This issue was referenced by PR #20529, which was included in the 10.52.0 release.
Metadata
Metadata
Assignees
Projects
- Status
Problem Statement
I'm using sentry's hono middleware for the http requests, but I can't find any information about how to wrap my queue endpoint to capture errors. I understand that this is not provided by default, but is there any workaround for the time being? Also, would you recommend using cloudflare sdk to wrap the fetch endoint or keep using the hono middleware?
Cheers,
Pau
Solution Brainstorm
no ideas, sorry :)