Hey. Mind sending your account ID (it's fine to make it public, it's not secret info) and I can see
Hey. Mind sending your account ID (it's fine to make it public, it's not secret info) and I can see if I can escalate this?

messages cannot be pulled unless http_pull mode is enabledhttp_pull, which I thought was the key to defining "http_pull mode":
8c720189e5c54eefa03f53eefb7162f1 that gives messages cannot be pulled unless http_pull mode is enabled. I even tried previewing and deleting the 3 messages in there, didn't help
Messages are delivered to the DLQ when they reach the configured retry limit for the consumer. Without a DLQ configured, messages that reach the retry limit are deleted permanently.

--remote, and got:Queues are currently in Beta and are not supported in wrangler dev remote mode.Given this, is there no way for me to test in development? I need
--remote for various other reasons; testing without that flag isn't an option.__schedule query string arg for testing CRON schedules locally.ms. More CPU-heavy things will increase it (for example, hashing passwords). This is not the same as the time a fetch request takes.max_batch_size = 1
max_retries = 0messages cannot be pulled unless http_pull mode is enabledmessages cannot be pulled unless http_pull mode is enabledhttp_pull8c720189e5c54eefa03f53eefb7162f1__schedulems{
"queue_id": "8c720189e5c54eefa03f53eefb7162f1",
"queue_name": "queue2-ci-dlq",
"settings": {},
"created_on": "2024-03-10T18:25:36.141403Z",
"modified_on": "2024-03-10T18:25:36.141403Z",
"producers_total_count": 0,
"producers": [],
"consumers_total_count": 1,
"consumers": [
{
"settings": {
"batch_size": 10,
"max_retries": 100,
"visibility_timeout_ms": 30000,
"retry_delay": 0
},
"consumer_id": "d2a3644fd6cc40fab4e023ce65c451dc",
"type": "http_pull"
}
]
}