good to know, thanks! don't think i saw this documented explicitly btw
good to know, thanks! don't think i saw this documented explicitly btw
MLet me fix!
FDo you happen to know how to get passed this issue with running tests with the Vitest Pool Workers library with Workflows that are bound to a Worker and DO? Adding it in causes a similar error to what fredviken is getting. Do I need to do any extra imports in the
Snippet of my wrangler.jsonc below
vitest.config file as I have the workflow in a separate folder? The durable object class gets resolved without issue, but not the workflow.Snippet of my wrangler.jsonc below
SAre there guarantees that in flight workflow requests are allowed to finish when a new worker version is deployed?
We're ready to migrate off Durable Objects in favor of Workflows because DOs don't have this guarantee; just wanted to make sure that Workflows actually do have this property
We're ready to migrate off Durable Objects in favor of Workflows because DOs don't have this guarantee; just wanted to make sure that Workflows actually do have this property
DwaitForEvent seems really powerful, but I can't figure out how it works exactly. To trigger the event, you need to know its instanceId, await env.MY_WORKFLOW.get(instanceId)m , but how will the external service know the instanceId that is determined by the workflow internally? Your example with Stripe here: https://developers.cloudflare.com/workflows/build/events-and-parameters/#send-events-to-running-workflows is interesting, but how would Stripe know what the instance id is to trigger?
Cloudflare Docs
When a Workflow is triggered, it can receive an optional event. This event can include data that your Workflow can act on, including request details, user data fetched from your database (such as D1 or KV) or from a webhook, or messages from a Queue consumer.
SCan multiple workers bind to workflows sharing the same name? For preview deploys, we currently spin up a new worker, but it shares a wrangler.toml as our production deploy, so we would have multiple workers with workflows of the same name.
This UI seems to imply that a given workflow can only have a single bound worker?
EDIT: seems like it can't. templating in our wrangler.toml seems to fix the issue...
This UI seems to imply that a given workflow can only have a single bound worker?
EDIT: seems like it can't. templating in our wrangler.toml seems to fix the issue...
IAre there any plans to lift or increase the current limit of 1,000 external requests per workflow instance? Right now, I'm having to split my workflows just to work around this restriction.
SBug report: workflows are not created in cloudflare when using gradual deploys, at least when created for the first time
MIn most cases you likely want a Worker to do the routing from webhook -> the correct instance, but if (for example) you can attach metadata to the Stripe payment event or subscription request, you can include the instance ID.
MYes, but will take a bit of time (weeks, not days).
Anow that workflows are GA/production ready, how can i delete a workflow?
DComing very soon
MWhat version of
wrangler
BIs there any sample to create workflow using api, as I am trying to make dynamic workflow where user can select how workflow will processed so does anyone have code sample or CURL or anything which can help me out?
DYeah, but the Stripe webhook that trigger the waitForEvent for a particular workflow instance will by definition fire after the workflow has already started. There is no way to put the instance id into Stripe metadata, because there is no way Stripe will have this information. You can't update stripe metadata before something you don't know will happen will happen. This is the case for nearly every single instance where you would use waitFor. The thing that will trigger the waitFor will fire AFTER the workflow starts or what are you waiting for? So there is no way the external event will ever know what the instance is. Reallly the only way I can see that this can possibly work is that both the Workflow and external event that will eventually trigger the waitForEvent both use a predetermined uniqueID that is considered unique across all workflows. In that way the Workflow instance Id would be created with that uniqueId. But this is quite challenging to get right. In the case of orders, I guess you will have a unique order ID that can possibly be shared by Stripe and the Workflow, but this would have to be created by a 3rd party system, so that Stripe and the Worfklow can both know it.
M- You can set your own instance IDs - you don’t have to create the instance first. For example, the Workflow ID can be the order ID so you have a 1:1 association with those. Or your customer ID, transaction ID, or any other stable identifier that you would otherwise use. Workflows is not unique here.
- and/or the Workflow itself can trigger the order, set the webhook, and then wait for the event
MI don’t think anything about this example code is impossible to achieve here.
M
Cloudflare Docs
You can trigger Workflows both programmatically and via the Workflows APIs, including:
BNo, I am not talking about trigger workflow, I want to create workflow script dynamically using script API.
like below I have make CURL for creating workflow script but getting error
like below I have make CURL for creating workflow script but getting error
Mhttps://developers.cloudflare.com/workers/configuration/multipart-upload-metadata/
- see here. You are also missing the Workflow definition. Otherwise, this isn’t specific to Workflows
Cloudflare Docs
If you're using the Workers Script Upload API or Version Upload API directly, multipart/form-data uploads require you to specify a metadata part. This metadata defines the Worker's configuration in JSON format, analogue to the wrangler.toml file.
FFollowing up on this, have updated Wrangler to the latest version (
4.10
Sin this case, I think that you need to update the
vitest-pool-workers
FSavior, that helped. This thing has been moving forward fast!
BOkay. thanks @Matt Silverlock
D"You can set your own instance ID" - OK that is not clear from the docs and examples. I think all the examples I have seen use crypto to create a unique instance. Also, I like the idea of the workflow triggering the actual order. Didn't think of that. Thanks!
FWhat we tend to do is use a shared UUID for various items and prefix with what the consumer is, e.g.,
workflow-${uuid}Where can we make this clearer? Documented here: https://developers.cloudflare.com/workflows/build/workers-api/#create
An ID is automatically generated, but a user-provided ID can be specified (up to 64 characters 1). This can be useful when mapping Workflows to users, merchants or other identifiers in your system.We kept the tutorial simpler (because otherwise we get feedback that we’re introducing too much!)
M100% this. Same as you would with Temporal or other async workflow systems.
DYeah, I see it there now. I'm not sure how you can make this clearer. It's easy to miss that. And also, I generally read examples first and learn from that, and don't go back to the docs unless I need something new or have a bug. And all the examples either don't create the instance and let it be done automatically or they use crypto. So that's how I've been doing it. Maybe have an example with an instance ID that is user-provided? Not really sure.
MYeah - maybe we can link out from the guide so it’s mentioned but doesn’t pollute the tutorial / add too much up front
MOr a code comment (or both)
FBoth the workers were using 4.9.1. I just tried updating to the latest (4.10.0) but I still get the same error message
FIs there a way to use the chrome debugger inside the workflow steps? I'm unable to hook into it from the main pool, but the worker and DOs work there. Trying to figure out why I'm not getting error logs in a dedicated class that's being called in the step.
BThe way I'm getting around the limit is popping messages into a queue and then batching 100 messages or every 10 seconds to a workflow. When hitting the ratelimit, the queue will redeliver in the next batch
BAlthough my usecase isn't time sensitive, it's handling user registrations
HWe can retry them, of course — but workflows are meant to be about durable execution. What I was expecting was a way to trigger multiple distinct workflows transactionally with a single request. That way, if the Cloudflare Workflows API goes down or we hit a quota/limit issue, either all workflows start or none do — instead of ending up in a half-started, inconsistent state.
By having to manage retries ourselves, we’re essentially recreating the very problem that workflows are supposed to solve, aren’t we?
By having to manage retries ourselves, we’re essentially recreating the very problem that workflows are supposed to solve, aren’t we?
MHow are you solving this today/elsewhere? What requires these Workflows to be tightly coupled in a way that can’t be solved by using one Workflow vs trying to spread across many?
(To be clear, this doesn’t mean we wouldn’t consider a transactional API, but it’s non-trivial across multiple unrelated Workflows, because that has a performance + complexity cost)
(To be clear, this doesn’t mean we wouldn’t consider a transactional API, but it’s non-trivial across multiple unrelated Workflows, because that has a performance + complexity cost)
JWhat's the best way to use Queues to limit the concurrency of Workflows? Or would it be just polling the workflow status and using setTimeout to sleep on the consumer before ack'ing the message?
JOhh yeah, that might work! I've just discovered
waitForEvent
IIs this released or coming in the future? "When creating a Workflow instance, you can set a shorter state retention period if you do not need to retain state for errored or completed Workflows."
MComing soon.
AHello, is there a subrequest limit on workflows? Trying to work out if it fits my use case which I expect to need to make several thousand subrequests to R2. I was looking at a scheduled worker job but I think that certainly does have a 1000 subrequest limit. The docs seem a little unclear in that there is no explicit limit here but it states "Many limits are inherited... [from Workers]".
Cloudflare Docs
Limits that apply to authoring, deploying, and running Workflows are detailed below.
DYep, the limit is the same as workers
AThanks!
SHow can we disable retries? Is is sufficient to set
We did this and still are still seeing retries in our dashboard.
retries0We did this and still are still seeing retries in our dashboard.
Jyou have to configure it for every step
MWhen we will be able to delete Workflows?
