Is there a way to delete a workflow? Used onto to send messages onto a queue and some during testing
Is there a way to delete a workflow? Used onto to send messages onto a queue and some during testing and want to just clean them up for my OCD 
Djust to clarify, it means that if you have 5k queued (scheduled workflows pass to queued, once they are intended to be run), 100 will be initially instructed to run, and as they complete, more will run?
DThis is not possible for the moment
SAh ok. Well, something you guys can add then.
Ahi! what is the unit of delay field in WorkflowStepConfig if its a number. the documentation at https://developers.cloudflare.com/workflows/build/sleeping-and-retrying/ says default is 10000 - is this ms?
Cloudflare Docs
This guide details how to sleep a Workflow and/or configure retries for a Workflow step.
SHi 
. Does anyone have a demo Remix repo I could learn from? (using remix-run/remix/templates/cloudflare-workers)
I have tried following @Craig's "punderful-workflows" example, and kept it very simple in the wrangler and the "main" JS file (following his example, but in a Remix repo)....
But no matter what I do, I always come up against this error....
If someone has a repo with workflows in a Remix setting, that would be much appreciated
. Does anyone have a demo Remix repo I could learn from? (using remix-run/remix/templates/cloudflare-workers)I have tried following @Craig's "punderful-workflows" example, and kept it very simple in the wrangler and the "main" JS file (following his example, but in a Remix repo)....
But no matter what I do, I always come up against this error....
Worker "workflows:interaction"'s binding "USER_WORKFLOW" refers to service "core:user:" with a named entrypoint "InteractionWorkflow", but "core:user:" has no such named entrypoint.If someone has a repo with workflows in a Remix setting, that would be much appreciated
MYou can’t deploy a Workflow as part of a Pages app (which is likely what the default Remix build is trying to do).
Deploy the Workflow separately (as a Worker) and bind to it from your Pages app / call it over HTTP.
Deploy the Workflow separately (as a Worker) and bind to it from your Pages app / call it over HTTP.
AI've been digging into workflows a lot, but recently I've been getting this error:
The destination execution context for this RPC was canceled while the call was still running.
ZHi Matt, the repo that I posted is using the latest Cloudflare Remix template using Workers instead of pages. And the issue was still occuring.
WThe Remix template is currently building as a Pages project then deploying as a Worker which is likely why this is happening. Remix has native support for Assets now so we're moving that over, you can track that here: https://github.com/cloudflare/workers-sdk/pull/7170
SAh thanks for the reply. Can I ask - what determines Pages vs Worker? I was previously looking for "pages_build_output_dir " in .wrangler
DI'm trying to understand how can I get workflow step by workflow id or is not possible?
Dwrangler workflows instances describe there is no equivalent for local right?
MNo automatic unique id is generate when create method is called without id. Is it a usual behaviour or a bug in local?
MI’m exploring Cloudflare Workflows to streamline email notifications for parents on our e-learning platform. Our goal is to notify parents based on specific events they’ve subscribed to, like when a student completes a quiz, finishes a topic, or needs a daily/weekly family summary. We want to set these notifications to trigger at defined times, tailored to each user’s preferences. If anyone has insights or tips on setting up these kinds of recurring notifications effectively, I’d love to hear them!
Thanks in advance for your help!
Thanks in advance for your help!
DWas doing some load tests and noticed that if I start a bunch of workflows quickly the dashboard kinda becomes really slow 
DAnyone else experience this? 
DI was only starting like 26/s tho 
DOnce I stop the load test and wait a few min for the workflows to finish .. it loads fine
Ois there some concurrency limit for workflows, and after that the ability to queue in items for processing? i have a cronjob that potentially fetches a lot of data to be processed at once and i want to send it to a workflow, but i don't want to hit the concurrency limit
Othis seems like exactly what i want but i can't seem to find the answer
Oadditionally is there a way to limit the amount of concurrent workflow runs overall? like if i have 100 waiting for API calls it won't start up more?
MNope, not yet. I think they are working on it.
Swe are aware of the performance issue and hopefully fixing it very :soonsoontm:
A
Awe're seeing a LOT of these "Attempt failed due to internal workflows error" failures
Afor days, in a great many of our workflow instances
Ais anyone else seeing this? does anyone have insight into what these errors are?
Ohey there. i'm working with a HTMLRewriter and i seem to be getting errors with an RPC stub not being disposed. i think it's the rewriter because of essentially the same error here. is this an issue on my side or an issue within workers?
DI also noticed... I have a sleep step like so
await step.sleep('wait on something', '1 second') but here it says the wall time for this step is 254ms .. any idea why it's lower than what the wall time should be?
Dit would also be nice if it showed the sleep step name (i.e - "wait on something").. even tho it is just a sleep.. instead of just showing the name as "Sleep"
DMaybe like
wait on something (Sleep)DIt's easy to tell what sleep step it is, since I only have 1 sleep step.. but if I had multiple.. it would be easier to tell which sleep step is what very quickly
AI hit a wall with Workflows:
What is the workaround for worklows? For service bindings, it is to use streams.
Serialized RPC arguments or return values are limited to 1MiB which I think happens when the returned values of a step are larger than 1MiB.What is the workaround for worklows? For service bindings, it is to use streams.
AYeah merged 3 steps into 1. Not ideal.
Swdym? in theory you can save/load in a different storage provider without compromising granularity
AIt's just a lot faff to add R2/offloading (not being used in this project).
SI understand, my future OSS side project that I've wanting to do might solve that: is to allow some nice abstractions on top of workflows (like natively supporting other storage providers, and other cool stuff that i've been noting down)
FHey ,
loving workflows so far, one thing I noticed is when you use the
While when I trigger it via cli, it works without any problems.
,loving workflows so far, one thing I noticed is when you use the
Trigger Button to trigger a workflow, the Params are submitted with some extra characters While when I trigger it via cli, it works without any problems.
1try a
JSON.parse() on the params first1But tbh not sure if the
Trigger button doing the stringify, or if wrangler not stringifying would count as a bug hereFThanks 
for the feedback. I think for the button you can only enter „valid json“ so a stringified version is not validated in the modal text input. But yeah you are right if i input a non stringified json, after clicking trigger it gets stringified which makes my workflow fail.
But the stringified cli trigger payload works
for the feedback. I think for the button you can only enter „valid json“ so a stringified version is not validated in the modal text input. But yeah you are right if i input a non stringified json, after clicking trigger it gets stringified which makes my workflow fail. But the stringified cli trigger payload works
LI noticed this as well. You can use a JSON parse when testing through the dashboard but keep in mind that this doesn’t happen when you are actually sending JSON to the workflow when you create a run so don’t leave it in for production
SIs workflows down, some of my requests ahve been stuck in queue for a few minutes and just aren't being procesed.
I am sending thousands of requests so there is some scale to it.
I am sending thousands of requests so there is some scale to it.
SAlso when running more than 2 workflows per second im getting throttled.
Sometimes responses from workflows rest API endpoint to start a new workflow is taking up to 40seconds
Sometimes responses from workflows rest API endpoint to start a new workflow is taking up to 40seconds
DHow many Workflows do you have running?
We are aware of the some performance issue under heavy load (per account) and we are working on fixes for it
We are aware of the some performance issue under heavy load (per account) and we are working on fixes for it
DIs this something new for you? I mean, did you see it in the past?
SFirst time I’ve ran a large workload
FIs there a way to re-run a workflow after sleep when the workflow has finished running?