[Brooooooklyn]

Problem

A queue file can set export const maxRetries = 0 or export const retryDelay = 30. On a Void-managed void deploy, both settings were left out of the deploy manifest, so the platform created the consumer with Cloudflare's defaults (3 retries, no delay). A consumer that asked for no retries was still retried.

before:
queues/emails.ts ──scan──> {maxBatchSize, maxBatchTimeout, maxRetries, retryDelay}
                 ──manifest──> {maxBatchSize, maxBatchTimeout}        (retries dropped)
                 ──platform──> Cloudflare defaults

after:
queues/emails.ts ──scan──> {maxBatchSize, maxBatchTimeout, maxRetries, retryDelay}
                 ──manifest──> {maxBatchSize, maxBatchTimeout, maxRetries, retryDelay}
                 ──platform──> max_retries / retry_delay as set

What changed

toManifestSchedulesAndQueues in packages/void/src/cli/deploy-helpers.ts now copies maxRetries and retryDelay when they are set. It uses != null, so 0 is kept. Native Cloudflare deploys already did this.

Tests

New unit test in packages/void/test/unit/deploy-project.test.ts:

• maxRetries: 0 and retryDelay: 30 appear in the manifest.
• A queue with no options gets no extra keys.

The test fails without the fix. It also fails if the check becomes truthy (so 0 is dropped), or if retryDelay is always written.

Choices to check

• No docs change: the queue guide already documents both options; this makes managed deploys match it.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-27T08:07:26.280425Z	d6900fc	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Brooooooklyn]

@codex review

[cloudflare-workers-and-pages]

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://fix-managed-queue-retries-void-cloud.voidzero-docs.workers.dev (commit d6900fc)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status	Deployment URL	Commit	Updated (UTC)	See this deployment's details
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://68887445-void-cloud.voidzero-docs.workers.dev	d6900fc	2026-10-27T08:07:23.052Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://d8104226-void-cloud.voidzero-docs.workers.dev	d85c1c9	2026-10-27T07:56:31.455Z	Visit the dashboard ↗
Build: Success ✅ Deployment: Success ✅ View logs ↗	https://5222633b-void-cloud.voidzero-docs.workers.dev	511fb0d	2026-10-27T07:21:26.639Z	Visit the dashboard ↗

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Bravo.

Reviewed commit: 511fb0d70e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

void/packages/void/src/auth/config.ts

Lines 104 to 105 in d85c1c9

	const config = await resolveConfig({ root, mode: 'development', logLevel: 'silent' }, 'serve');
	return viteAuthConfigImporter(root, config.mode, config.resolve)(path);

Keep standalone preparation independent of Vite configuration

For apps with an auth config, prepareProject() now reaches this call during void prepare, evaluating the application's Vite config and running its plugin configuration hooks. This violates the explicit packages/void/AGENTS.md invariant that “void prepare boots no Vite.” It also introduces real configuration side effects into standalone type generation: the built-in voidPlugin() materializes Cloudflare configuration and creates dev-trigger state during construction. Keep the standalone preparation path independent of application Vite initialization rather than invoking the full serve configuration to obtain aliases.

AGENTS.md reference: packages/void/AGENTS.md:L169-L169

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Brooooooklyn]

Fixed in 106d132 on #611, which this PR is stacked on. void prepare, void gen and void db generate no longer load the app's vite.config: auth.ts is evaluated with Vite's runnerImport (no config file), using tsconfig paths and Void's own @schema alias. The prepare test now has a vite.config that writes a marker file and checks it is never written.