Too Many Requests when you hit the rate limit. Did you exceed your backlog in a single queue?
Too Many Requests
J
Queue send failed: Queue is overloaded. Please back off..send.send.send
MMM
M
SS
J
CCC
C
ZMMMM
add()add()send()
We'll have more updates to share publicly next week.M
UU
WWM
VV
KMMS
Pull consumers are designed to use a "short polling" approach, this means that the API from CloudFlare will respond immediately with any messages that are available, or an empty response if there are no messages available, this is different from SQS will wait an amount of time before responding with an empty response.). is that something that http pull would benefit from here? or are you of the opinion that fast-response > quantity of requests is more important.S
MSS
MMMMMMM
for (const msg of batch.messages) {➜ curl "https://api.cloudflare.com/client/v4/accounts/${CF_ACCOUNT_ID}/queues/${QUEUE_ID}/messages/pull" -X POST --data '{}' \
-H "Authorization: Bearer ${QUEUES_TOKEN}" \
-H "Content-Type:application/json"// Delay a singular message by 600 seconds (10 minutes)
await env.YOUR_QUEUE.send(message, { delaySeconds: 600 })export default {
async queue(batch: MessageBatch, env: Env, ctx: ExecutionContext) {
for (const msg of batch.messages) {
// Mark for retry and delay a singular message
// by 3600 seconds (1 hour)
msg.retry({delaySeconds: 3600})
}
},
}; Pull consumers are designed to use a "short polling" approach, this means that the API from CloudFlare will respond immediately with any messages that are available, or an empty response if there are no messages available, this is different from SQS will wait an amount of time before responding with an empty response.