For Workes & Pages, what is the name of the domain?
What is the issue or error you’re encountering
Messages Not Moving to Dead Letter Queue After Max Retries
What are the steps to reproduce the issue?
I’m experiencing an issue with Cloudflare Workers Queues where messages in my primary queue (mqueue
) do not move to the Dead Letter Queue (mqueue-dlq
) after reaching the maximum retry limit.
Context and Configuration:
I have set up a Cloudflare Worker with the following queue configuration:
-
Producer Configuration:
queues.producers = [ { queue = 'mqueue', binding = 'QUEUE_PAYMENT' }, ]
-
Consumer Configuration:
queues.consumers = [ { queue = 'mqueue', dead_letter_queue = 'mqueue-dlq', max_batch_size = 10, max_batch_timeout = 1, max_retries = 3 }, ]
Problem:
- I’ve confirmed through logging that the messages in the
mqueue
queue are throwing errors and have reached the maximum retry count of 3. - Despite this, the messages do not appear in the Dead Letter Queue (
mqueue-dlq
) as expected.
What I’ve Tried:
-
Checked the Configuration:
- Verified the
dead_letter_queue
andmax_retries
settings in both mywrangler.toml
file and the Cloudflare Dashboard. - Ensured that the
mqueue-dlq
queue is correctly created and configured.
- Verified the
-
Re-deployed the Worker:
- Re-deployed my Cloudflare Worker with the updated configuration to ensure that all settings were properly applied.
-
Verified Logs:
- Observed in the logs that the messages in the
mqueue
queue have been retried 3 times and failed each time.
- Observed in the logs that the messages in the
-
Tested with Manual Errors:
- Manually sent test messages to the
mqueue
queue, induced errors, and confirmed that they were retried 3 times, but still did not move to the Dead Letter Queue.
- Manually sent test messages to the
Request for Assistance:
Could anyone help me understand why the messages are not moving to the Dead Letter Queue after the maximum retries? Is there any additional configuration or step I might be missing?