12 replies

hmm, it seems like my messages are being

hmm, it seems like my messages are being retried immediately after an implicit retry instead of waiting the configured 60 seconds..

[[env.staging.queues.consumers]]
queue = "emails-staging"
max_batch_size = 1
max_concurrency = 1
dead_letter_queue = "emails-dlq-staging"
max_retries = 5
retry_delay = 60

[[env.staging.queues.consumers]]
queue = "emails-staging"
max_batch_size = 1
max_concurrency = 1
dead_letter_queue = "emails-dlq-staging"
max_retries = 5
retry_delay = 60

[[env.staging.queues.consumers]]
queue = "emails-staging"
max_batch_size = 1
max_concurrency = 1
dead_letter_queue = "emails-dlq-staging"
max_retries = 5
retry_delay = 60

[[env.staging.queues.consumers]]
queue = "emails-staging"
max_batch_size = 1
max_concurrency = 1
dead_letter_queue = "emails-dlq-staging"
max_retries = 5
retry_delay = 60

johtsoOP•9/5/24, 3:03 PM

id: 46ff84346aa373686c92055cc6259252

johtsoOP•9/5/24, 3:03 PM

2024-09-05T15:02:09.183Z

johtsoOP•9/19/24, 10:09 AM

@Pranshu Maheshwari any chance of getting some eyes on this when you have a moment?

johtsoOP•9/19/24, 10:10 AM

I'm relying on the queue configuration to stop me spamming my APIs if there are failures

johtsoOP•9/19/24, 10:11 AM

Retry delay seems to be ignored for some reason

Pranshu Maheshwari•9/19/24, 2:50 PM

hey, thanks for the ping, I totally missed this

Pranshu Maheshwari•9/19/24, 2:52 PM

you probably checked this already, but just in case: when marking a message to be retried, you're not setting delaySecondsdelaySeconds on the individual message right?

Pranshu Maheshwari•9/19/24, 2:53 PM

also, is this happening locally or when you deploy your consumer? there's a known issue with local consumers & retry delays (which is expected to be fixed by next week)

Sid•9/20/24, 4:01 PM

I was just looking into this, and can't seem to repro during local dev or after deployment, interestingly

Sid•9/20/24, 4:02 PM

My Worker is really simple:

type Env = {
  Q: Queue<string>;
};

export default {
  async fetch(request: Request, env: Env) {
    console.log("Pushing to queue");
    await env.Q.send("1");
    return new Response("1");
  },

  async queue(messages: MessageBatch) {
    console.log(`[${Date.now()}] Processing`, JSON.stringify(messages));
    messages.retryAll();
  },
} satisfies ExportedHandler<Env>;

type Env = {
  Q: Queue<string>;
};

export default {
  async fetch(request: Request, env: Env) {
    console.log("Pushing to queue");
    await env.Q.send("1");
    return new Response("1");
  },

  async queue(messages: MessageBatch) {
    console.log(`[${Date.now()}] Processing`, JSON.stringify(messages));
    messages.retryAll();
  },
} satisfies ExportedHandler<Env>;

wrangler.toml:

[[queues.producers]]
queue = "playground"
binding = "Q"

[[queues.consumers]]
queue = "playground"
max_retries = 5
retry_delay = 5

[[queues.producers]]
queue = "playground"
binding = "Q"

[[queues.consumers]]
queue = "playground"
max_retries = 5
retry_delay = 5

Sid•9/20/24, 4:03 PM

Can you try logging the message.attemptsmessage.attempts to make sure you don't have similar-looking messages?

Sid•9/20/24, 4:04 PM

Also message.timestampmessage.timestamp might also help

Sid•9/20/24, 4:20 PM

Tried individual message.retrymessage.retrys as well, that also seems to work as expected

hmm, it seems like my messages are being

Similar Threads