Skip to content

improve: bump up maximum allowed value for Queue delivery and retry delay to 24 hours#12597

Merged
dario-piotrowicz merged 1 commit intocloudflare:mainfrom
sdnts:main
Feb 18, 2026
Merged

improve: bump up maximum allowed value for Queue delivery and retry delay to 24 hours#12597
dario-piotrowicz merged 1 commit intocloudflare:mainfrom
sdnts:main

Conversation

@sdnts
Copy link
Copy Markdown
Contributor

@sdnts sdnts commented Feb 18, 2026

Fixes MQ-1097

Queues can now accept delivery delays up to 24 hours


A picture of a cute animal (not mandatory, but encouraged)


Open with Devin

@sdnts sdnts requested a review from a team as a code owner February 18, 2026 13:25
@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Feb 18, 2026

🦋 Changeset detected

Latest commit: 6dfb7f0

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 2 potential issues.

⚠️ 2 issues in files not directly in the diff

⚠️ Hardcoded old max delay (43200) in CLI help text for queues create command (packages/wrangler/src/queues/cli/commands/create.ts:34)

The --delivery-delay-secs argument description in queues create still says "Must be between 0 and 43200" even though MAX_DELIVERY_DELAY_SECS was bumped to 86400.

Root Cause

The constant MAX_DELIVERY_DELAY_SECS at packages/wrangler/src/queues/constants.ts:5 was updated from 43200 to 86400, and the validation error messages at packages/wrangler/src/queues/cli/commands/create.ts:99 correctly use the constant via string interpolation. However, the describe string for the --delivery-delay-secs argument at line 34 has the old value hardcoded as "Must be between 0 and 43200".

Impact: Users running wrangler queues create --help will see the old maximum of 43200 (12 hours), but the actual validation accepts up to 86400 (24 hours). This creates confusion where the help text tells users the max is 12 hours but the system actually accepts 24 hours.


⚠️ Hardcoded old max delay (43200) in CLI help text for queues update command (packages/wrangler/src/queues/cli/commands/update.ts:29)

The --delivery-delay-secs argument description in queues update still says "Must be between 0 and 43200" even though MAX_DELIVERY_DELAY_SECS was bumped to 86400.

Root Cause

Same issue as in create.ts — the constant MAX_DELIVERY_DELAY_SECS at packages/wrangler/src/queues/constants.ts:5 was updated from 43200 to 86400, and the validation error message at packages/wrangler/src/queues/cli/commands/update.ts:79 correctly uses the constant. However, the describe string for the --delivery-delay-secs argument at line 29 has the old value hardcoded as "Must be between 0 and 43200".

Impact: Users running wrangler queues update --help will see the old maximum of 43200 (12 hours), but the actual validation accepts up to 86400 (24 hours).

View 3 additional findings in Devin Review.

Open in Devin Review

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new bot commented Feb 18, 2026

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@12597

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@12597

miniflare

npm i https://pkg.pr.new/miniflare@12597

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@12597

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@12597

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@12597

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@12597

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@12597

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@12597

wrangler

npm i https://pkg.pr.new/wrangler@12597

commit: 6dfb7f0

Copy link
Copy Markdown
Member

@dario-piotrowicz dario-piotrowicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thanks @sdnts 🙂

@github-project-automation github-project-automation bot moved this from Untriaged to Approved in workers-sdk Feb 18, 2026
Copy link
Copy Markdown
Contributor

@jkoe-cf jkoe-cf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I approve

@dario-piotrowicz dario-piotrowicz merged commit 0b17117 into cloudflare:main Feb 18, 2026
41 of 43 checks passed
@github-project-automation github-project-automation bot moved this from Approved to Done in workers-sdk Feb 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants