not just delay, I mean if the http pull isn't available and doesn't come online for 1h-24h
not just delay, I mean if the http pull isn't available and doesn't come online for 1h-24h

fetch() and a queue() ? the fetch is a simple web page. I'm have a litte troubble understanding what happens when the queue forces the worker to scale? Is there any potential problems there?json, from the existing v8 default. This will improve compatibility with pull-based consumers when we release them.2024-03-04{ task_id, subtask_data }, and when I call sendBatch all messages in the batch have the same task_id, then can I guarantee that all messages in the consumer have the same task_id? Or will retries or max batch sizes mess with this?.send to a queue. (that if I understood it right) must be awaited...send takes between 200ms and 300ms


Queue environment binding limit the colos where the producing fetch handler can run, or change the behavior of the worker in any way?queue handler (consumer) in the same worker as an existing fetch handler limit where the fetch handler can run, or change the behavior of the fetch side of the worker in any way?platform:dev: ✘ [ERROR] Uncaught (async) Error: Handler does not export a queue() function.
platform:dev:
[wrangler-UserWorker:wrn] Dropped message "e1d974b8e338ba4bd883f45d1f630728" on queue "queue" after 3 failed attempts!Queue