telliks
CDCloudflare Developers
•Created by telliks on 3/26/2025 in #queues
Pretty sure something got broken with
Thank you! I’ll keep an eye on it and let you know if I see any more issues.
11 replies
CDCloudflare Developers
•Created by telliks on 3/26/2025 in #queues
Pretty sure something got broken with
Thanks!
11 replies
CDCloudflare Developers
•Created by telliks on 3/26/2025 in #queues
Pretty sure something got broken with
There is not really much more in the logs. The Worker logs don't show much and the error from the Workflows step is exactly what I sent above.
11 replies
CDCloudflare Developers
•Created by telliks on 3/26/2025 in #queues
Pretty sure something got broken with
1. It is a single worker that acts as both the producer and consumer. I write to the queue in a Workflows step.
2. I tested now and could send to the queue directly in the Cloudflare console. So it is likely something throwing the moment it tries to send to the queue from the Workflow.
11 replies
CDCloudflare Developers
•Created by telliks on 3/26/2025 in #queues
Pretty sure something got broken with
Sure, thank you.
Queue ID: f0b59780627e4c47bf6676580a042ef7
Account ID: a740bb7c74be61f4aa56f3cda1892b3c
11 replies
CDCloudflare Developers
•Created by telliks on 12/4/2024 in #workflows
DLQ Equivalent
Looking forward to it. It will make workflows even better.
The reason I proposed the optional error callback on the step level is because my mental model of Workflows are that it is essentially an orchestration of dynamic queues/steps. For that reason, it would be nice if each step has meta information about
attempts, etc, analogous to how message currently work for queue batches.3 replies
CDCloudflare Developers
•Created by telliks on 12/4/2024 in #workflows
DLQ Equivalent
It would be very useful.
A proposed API could be to have an error callback for the step's
do method, which is invoked whenever the step fails. It could show the retry count and whether it is a final invocation.
3 replies
CDCloudflare Developers
•Created by telliks on 11/28/2024 in #workers-observability
Logs for OpenNext app
Just for future reference. Logs started working after upgrading to Workers Paid. Not sure why.
1 replies
CDCloudflare Developers
•Created by telliks on 11/20/2024 in #workflows
Sure, I can share some pieces that I
Yeah, thanks I solved the issue. My problem was that the wrangler version pinned in my CI/CD pipeline was too old. That code snippet was just an example because it never even reached this point.
13 replies
CDCloudflare Developers
•Created by telliks on 11/20/2024 in #workflows
Sure, I can share some pieces that I
Thanks for help checking anyways
13 replies
CDCloudflare Developers
•Created by telliks on 11/20/2024 in #workflows
Sure, I can share some pieces that I
Yeah, I think it has something to do with this command:
npm create cloudflare@latest workflows-starter -- --template "cloudflare/workflows-starter"
AFAIK, that just creates a new worker but uses the given template. Since I already had a worker, I did not run this command and just tried adding the workflow config to my existing worker. Maybe that command does more just scaffold the project structure locally.13 replies