I mean, I think there's a big gap between never letting things expire and expiring everything for a

Cccarse I mean, I think there's a big gap between never letting things expire and expiri...

M

I can't reproduce that in the same invocation (nor should I be able to): instances persist during the running

wrangler dev

wrangler dev

run:

M

Matt Silverlock•4/10/25, 4:57 PM

If you change the code, that's a new invocation (reload of all state)

C

ccarseOP•4/10/25, 4:58 PM

Oh I wouldn't call that a new invocation, I only invoked it once.

M

Matt Silverlock•4/10/25, 4:58 PM

I understand where you're coming from, but I'm also explaining why this is the case

C

ccarseOP•4/10/25, 4:58 PM

Like, for example, my kv data doesn't disappear on each invocation right?

M

Matt Silverlock•4/10/25, 4:58 PM

Will chat w/ the team about options to opt-in to persistency here

C

ccarseOP•4/10/25, 4:58 PM

Why do instances?

Cccarse Why do instances?

M

Matt Silverlock•4/10/25, 4:59 PM

Instances aren't just state on disk (unlike KV pairs) - again, understand the frustration but not the same thing.

C

ccarseOP•4/10/25, 5:02 PM

I really like the products you all are putting out but it's frustrating how every product behaves differently in terms of local vs remote vs what is default and what's available. I know it's early days for workflows but just wanted to give the feedback.

C

ccarseOP•4/10/25, 5:29 PM

Is there a way to list recently invoked workflow instances in dev? I can use the api in prod but that doesn't work for dev.

MMatt Silverlock Show your `wrangler` config and code.

F

fredviken•4/10/25, 5:47 PM

These are the wrangler configs. the workflow is just a simple placeholder one for now with a console log and sleep, but it works like expected when called in the same worker. But the second i add the binding in the other worker it crashes, despite being able to connect using service bindings

Ffredviken These are the wrangler configs. the workflow is just a simple placeholder one fo...

M

Matt Silverlock•4/10/25, 6:17 PM

Thanks - taking a look!

MMatt Silverlock Call `.create` as needed for each Workflow.

H

hugo martins•4/10/25, 6:58 PM

Will this make only one request? If not, then there's a possibility that one of the requests might fail.

V

Victor•4/10/25, 7:03 PM

I'm trying to list or terminate workflows (both via rest api and via dashboard) returns

HTTP 500/10001 workflows.api.error.internal_server

HTTP 500/10001 workflows.api.error.internal_server

V

Victor•4/10/25, 7:08 PM

Now getting 503 service unavailable (7010 service unavailable)

V

Victor•4/10/25, 7:15 PM

Ok, any workflows action, even creating workflows from inside a worker (via binding) throws errors

Hhugo martins Will this make only one request? If not, then there's a possibility that one of ...

M

Matt Silverlock•4/10/25, 7:36 PM

One request per Workflow. You can retry any that fail (although that should be very rare). How would you expect this to be solved?

MMatt Silverlock @Workflows - Workflows is GA + we've shipped the new `step.waitForEvent` (and `i...

A

ajay | dreamlit.ai•4/10/25, 9:53 PM

Wooo! Congrats on the launch excited for this

Ffredviken These are the wrangler configs. the workflow is just a simple placeholder one fo...

F

felixnorden•4/10/25, 10:01 PM

Getting similar issues when using the Vitest Pool Workers lib for testing my workflow that's triggered by a Durable Object.

F

felixnorden•4/10/25, 10:01 PM

Lmk if you solve this, it has me stuck :kek:

MMatt Silverlock @Workflows - Workflows is GA + we've shipped the new `step.waitForEvent` (and `i...

S

s̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜•4/10/25, 10:02 PM

is

env

env

inside a workflow context? we would like to use our KV bindings

S

s̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜•4/10/25, 10:03 PM

congrats on the launch btw!

Ss̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜is `env` inside a workflow context? we would like to use our KV bindings

M

Matt Silverlock•4/10/25, 10:04 PM

this.env

this.env

ensuring you pass your
```
Env
```
```
Env
```
type as a parameter to your Workflow class: https://developers.cloudflare.com/workflows/build/workers-api/#workflowentrypoint

Cloudflare Docs

Workers API · Cloudflare Workflows docs

This guide details the Workflows API within Cloudflare Workers, including methods, types, and usage examples.

M

Matt Silverlock•4/10/25, 10:04 PM

Example usage: https://developers.cloudflare.com/workflows/examples/backup-d1/

Cloudflare Docs

Export and save D1 database · Cloudflare Workflows docs

Send invoice when shopping cart is checked out and paid for

MMatt Silverlock `this.env` - ensuring you pass your `Env` type as a parameter to your Workflow c...

S

s̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜•4/10/25, 10:05 PM

good to know, thanks! don't think i saw this documented explicitly btw

Ss̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜good to know, thanks! don't think i saw this documented explicitly btw

M

Matt Silverlock•4/10/25, 10:05 PM

Let me fix!

MMatt Silverlock Thanks - taking a look!

F

felixnorden•4/10/25, 10:47 PM

Do 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

vitest.config

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

{
  // Other info
  // ...
  "compatibility_date": "2025-03-17",
  "compatibility_flags": ["nodejs_compat"],

  "observability": {
    "enabled": true
  },

  "durable_objects": {
    "bindings": [
      {
        "name": "TASKS",
        "class_name": "Task"
      }
    ]
  },

  "migrations": [
    {
      "new_sqlite_classes": ["Task"],
      "tag": "v1"
    }
  ],

  "workflows": [
    {
      "binding": "TASK_WORKFLOW",
      "class_name": "TaskWorkflow",
      "name": "task-workflow"
    }
  ],
// Some other bindings with Queues, Services and Rules
// ...
}

{
  // Other info
  // ...
  "compatibility_date": "2025-03-17",
  "compatibility_flags": ["nodejs_compat"],

  "observability": {
    "enabled": true
  },

  "durable_objects": {
    "bindings": [
      {
        "name": "TASKS",
        "class_name": "Task"
      }
    ]
  },

  "migrations": [
    {
      "new_sqlite_classes": ["Task"],
      "tag": "v1"
    }
  ],

  "workflows": [
    {
      "binding": "TASK_WORKFLOW",
      "class_name": "TaskWorkflow",
      "name": "task-workflow"
    }
  ],
// Some other bindings with Queues, Services and Rules
// ...
}

{
  // Other info
  // ...
  "compatibility_date": "2025-03-17",
  "compatibility_flags": ["nodejs_compat"],

  "observability": {
    "enabled": true
  },

  "durable_objects": {
    "bindings": [
      {
        "name": "TASKS",
        "class_name": "Task"
      }
    ]
  },

  "migrations": [
    {
      "new_sqlite_classes": ["Task"],
      "tag": "v1"
    }
  ],

  "workflows": [
    {
      "binding": "TASK_WORKFLOW",
      "class_name": "TaskWorkflow",
      "name": "task-workflow"
    }
  ],
// Some other bindings with Queues, Services and Rules
// ...
}

{
  // Other info
  // ...
  "compatibility_date": "2025-03-17",
  "compatibility_flags": ["nodejs_compat"],

  "observability": {
    "enabled": true
  },

  "durable_objects": {
    "bindings": [
      {
        "name": "TASKS",
        "class_name": "Task"
      }
    ]
  },

  "migrations": [
    {
      "new_sqlite_classes": ["Task"],
      "tag": "v1"
    }
  ],

  "workflows": [
    {
      "binding": "TASK_WORKFLOW",
      "class_name": "TaskWorkflow",
      "name": "task-workflow"
    }
  ],
// Some other bindings with Queues, Services and Rules
// ...
}

S

s̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜•4/10/25, 11:38 PM

Are 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

D

ddsgadget•4/11/25, 2:02 AM

waitForEvent 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

Events and parameters · Cloudflare Workflows 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.

S

s̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜•4/11/25, 3:50 AM

Can 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...

I

inaridiy•4/11/25, 5:49 AM

Are 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.

S

s̸̘̩̓̍ẻ̸͕ͅå̶̡͖ṅ̴̹̊͜•4/11/25, 6:22 AM

Bug report: workflows are not created in cloudflare when using gradual deploys, at least when created for the first time

Dddsgadget waitForEvent seems really powerful, but I can't figure out how it works exactly....

M

Matt Silverlock•4/11/25, 6:24 AM

In 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.

Iinaridiy Are there any plans to lift or increase the current limit of 1,000 external requ...

M

Matt Silverlock•4/11/25, 6:25 AM

Yes, but will take a bit of time (weeks, not days).

A

Avi•4/11/25, 7:53 AM

now that workflows are GA/production ready, how can i delete a workflow?

AAvi now that workflows are GA/production ready, how can i delete a workflow?

D

Diogo Ferreira•4/11/25, 8:25 AM

Coming very soon

Ffredviken These are the wrangler configs. the workflow is just a simple placeholder one fo...

M

Matt Silverlock•4/11/25, 10:13 AM

What version of

wrangler

wrangler

are you using? Make sure it’s the latest (4.8.0 or later).

B

ByteBeast•4/11/25, 10:20 AM

Is 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?

MMatt Silverlock In most cases you likely want a Worker to do the routing from webhook -> the cor...

D

ddsgadget•4/11/25, 10:24 AM

Yeah, 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.

Dddsgadget Yeah, but the Stripe webhook that trigger the waitForEvent for a particular work...

M

Matt Silverlock•4/11/25, 10:33 AM

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

M

Matt Silverlock•4/11/25, 10:33 AM

I don’t think anything about this example code is impossible to achieve here.

BByteBeast Is there any sample to create workflow using api, as I am trying to make dynamic...

M

Matt Silverlock•4/11/25, 10:34 AM

https://developers.cloudflare.com/workflows/build/trigger-workflows/

take a look here

Cloudflare Docs

Trigger Workflows · Cloudflare Workflows docs

You can trigger Workflows both programmatically and via the Workflows APIs, including:

B

ByteBeast•4/11/25, 10:46 AM

No, 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

curl --location --request PUT 'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/workers/scripts/$SCRIPT_NAME' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Cookie: __cf_bm=BSfapaLrMo7TSHNizMMBSDc1VeGd1iZ6NaF3xErfwlM-1744368032-1.0.1.1-nBYMctsOJZrcH3agouhImrXCYRzeXROKf6uvM4XyDAogoTECkKmo4Fm7q0Vd.XqD6wF1q8urMUiYbpy68QKLd_Opw9i2Y01dtzBoyALEr8Y; __cflb=0H28vgHxwvgAQtjUGUFqYFDiSDreGJnUm6uGcveaJY5; _cfuvid=O4jwRzC_mJfhR25Kh5F.1IIpmpts7JbjH_QwbrurGgk-1744345016081-0.0.1.1-604800000' \
--form 'metadata="{ \"compatibility_date\": \"2021-01-01\", \"compatibility_flags\": [ \"nodejs_compat\" ], \"main_module\": \"worker.ts\" } "' \
--form 'script="export class MyWorkflow extends WorkflowEntrypoint<Env, Params> {
  async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
    // Steps here
    let someComputedState = step.do(\"my step\", async () => { })

    // Optional: return state from our run() method
    return someComputedState
  }
};"'

curl --location --request PUT 'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/workers/scripts/$SCRIPT_NAME' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Cookie: __cf_bm=BSfapaLrMo7TSHNizMMBSDc1VeGd1iZ6NaF3xErfwlM-1744368032-1.0.1.1-nBYMctsOJZrcH3agouhImrXCYRzeXROKf6uvM4XyDAogoTECkKmo4Fm7q0Vd.XqD6wF1q8urMUiYbpy68QKLd_Opw9i2Y01dtzBoyALEr8Y; __cflb=0H28vgHxwvgAQtjUGUFqYFDiSDreGJnUm6uGcveaJY5; _cfuvid=O4jwRzC_mJfhR25Kh5F.1IIpmpts7JbjH_QwbrurGgk-1744345016081-0.0.1.1-604800000' \
--form 'metadata="{ \"compatibility_date\": \"2021-01-01\", \"compatibility_flags\": [ \"nodejs_compat\" ], \"main_module\": \"worker.ts\" } "' \
--form 'script="export class MyWorkflow extends WorkflowEntrypoint<Env, Params> {
  async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
    // Steps here
    let someComputedState = step.do(\"my step\", async () => { })

    // Optional: return state from our run() method
    return someComputedState
  }
};"'

curl --location --request PUT 'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/workers/scripts/$SCRIPT_NAME' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Cookie: __cf_bm=BSfapaLrMo7TSHNizMMBSDc1VeGd1iZ6NaF3xErfwlM-1744368032-1.0.1.1-nBYMctsOJZrcH3agouhImrXCYRzeXROKf6uvM4XyDAogoTECkKmo4Fm7q0Vd.XqD6wF1q8urMUiYbpy68QKLd_Opw9i2Y01dtzBoyALEr8Y; __cflb=0H28vgHxwvgAQtjUGUFqYFDiSDreGJnUm6uGcveaJY5; _cfuvid=O4jwRzC_mJfhR25Kh5F.1IIpmpts7JbjH_QwbrurGgk-1744345016081-0.0.1.1-604800000' \
--form 'metadata="{ \"compatibility_date\": \"2021-01-01\", \"compatibility_flags\": [ \"nodejs_compat\" ], \"main_module\": \"worker.ts\" } "' \
--form 'script="export class MyWorkflow extends WorkflowEntrypoint<Env, Params> {
  async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
    // Steps here
    let someComputedState = step.do(\"my step\", async () => { })

    // Optional: return state from our run() method
    return someComputedState
  }
};"'

curl --location --request PUT 'https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/workers/scripts/$SCRIPT_NAME' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Cookie: __cf_bm=BSfapaLrMo7TSHNizMMBSDc1VeGd1iZ6NaF3xErfwlM-1744368032-1.0.1.1-nBYMctsOJZrcH3agouhImrXCYRzeXROKf6uvM4XyDAogoTECkKmo4Fm7q0Vd.XqD6wF1q8urMUiYbpy68QKLd_Opw9i2Y01dtzBoyALEr8Y; __cflb=0H28vgHxwvgAQtjUGUFqYFDiSDreGJnUm6uGcveaJY5; _cfuvid=O4jwRzC_mJfhR25Kh5F.1IIpmpts7JbjH_QwbrurGgk-1744345016081-0.0.1.1-604800000' \
--form 'metadata="{ \"compatibility_date\": \"2021-01-01\", \"compatibility_flags\": [ \"nodejs_compat\" ], \"main_module\": \"worker.ts\" } "' \
--form 'script="export class MyWorkflow extends WorkflowEntrypoint<Env, Params> {
  async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
    // Steps here
    let someComputedState = step.do(\"my step\", async () => { })

    // Optional: return state from our run() method
    return someComputedState
  }
};"'

BByteBeast No, I am not talking about trigger workflow, I want to create workflow script dy...

M

Matt Silverlock•4/11/25, 10:48 AM

https://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

Multipart upload metadata · Cloudflare Workers 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.

Ffelixnorden Do you happen to know how to get passed this issue with running tests with the V...

F

felixnorden•4/11/25, 10:51 AM

Following up on this, have updated Wrangler to the latest version (

4.10

4.10

4.10

4.10) but still getting the same errors for running my tests when introducing the workflow

Ffelixnorden Following up on this, have updated Wrangler to the latest version (`4.10`) but s...

S

Seekerdasbatatas•4/11/25, 10:54 AM

in this case, I think that you need to update the

vitest-pool-workers

vitest-pool-workers

vitest-pool-workers

vitest-pool-workers package

SSeekerdasbatatas in this case, I think that you need to update the `vitest-pool-workers` package

F

felixnorden•4/11/25, 10:59 AM

Savior, that helped. This thing has been moving forward fast!

MMatt Silverlock https://developers.cloudflare.com/workers/configuration/multipart-upload-metadat...

B

ByteBeast•4/11/25, 11:03 AM

Okay. thanks @Matt Silverlock

MMatt Silverlock 1. You can set your own instance IDs - you don’t have to create the instance fir...

D

ddsgadget•4/11/25, 11:11 AM

"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!

Dddsgadget "You can set your own instance ID" - OK that is not clear from the docs and exam...

F

felixnorden•4/11/25, 11:13 AM

What we tend to do is use a shared UUID for various items and prefix with what the consumer is, e.g.,

workflow-${uuid}

workflow-${uuid}

workflow-${uuid}

workflow-${uuid} so you can debug more easily too if/when things go south

I mean, I think there's a big gap between never letting things expire and expiring everything for a

Similar Threads

Similar Threads

Similar Threads