Pretty sure Workflows is built off of Queues. So read docs of both and weigh up pros and cons of you

Ttadhglewis Pretty sure Workflows is built off of Queues. So read docs of both and weigh up ...

M

It’s not, but it shouldn’t matter how it’s built. It’s a bit hard to understand the “why” behind what the other poster is asking though.

Sometimes you use both: Queues that can kick off Workflows to do the work on batches of <items>

RRahul gangotri How can we use cloudflare queue or workflow to process my users campaign where e...

O

Ollie•5/4/25, 5:01 PM

I would personally say workflows (and queues) are not ready for that kind of volume, they simply cant scale right now. Funnily enough workflows when they were in their BETA period were a pretty flawless platform, but since last week, only around 20% of our workflows ever actually run, around 50% get stuck, and then the other 30% don't even trigger (if you are using dead-letter-queues they end up getting filled up).

You will also never manage 4,500 instances running at the same time, we got up to say 350ish running at the same time, the rest just queued.

Until they fix the issues of scale, maybe consider another platform. Our company has basically had to turn some features off, that we built entirely on workflows and queues, and we are now considering something like temporal.

From my screenshot you can see we have over 5K stuck workflows, and we have around 3K+ messages in dead letter queues because workflows failed to even be instantiated. Before last week we ran nearly 1 million workflows in a month.

If they can get the issues sorted out, its probably the best workflow and queue platform l have used.

OOllie I would personally say workflows (and queues) are not ready for that kind of vol...

R

Rahul gangotri•5/4/25, 5:32 PM

, i am running bullmq for now buts its failing, otherwise i have to scale that or run kafka until this is resolved

I dont wanna use this until the issues are fixed otherwise i will end up having same issue after the migration

N

noskovvkirill•5/5/25, 12:23 AM

Hi guys! Is there any plan to add a middleware support to workflows? Similar to inngest (https://www.inngest.com/docs/features/middleware)? I need a persistent connection to my DB instance. Thanks

Sscook 🐛 It appears to be a bug? This happened multiple times. When I first deployed a...

T

tyx•5/5/25, 1:09 AM

I am getting a very confusing bug. I am getting.

Error: (workflow.not_found) Provided Workflow does not exist

Error: (workflow.not_found) Provided Workflow does not exist

when deployed but If I run it locally (but on remote mode) i detects the workflow and triggers it successfully. (i've tried re-deploying without success)

Is this a bug on CF side, seems like it?

T

tyx•5/5/25, 1:12 AM

shared my id with @Diogo Ferreira

I

Isak•5/5/25, 7:00 AM

When a workflow is awakened from sleep, does that count as a separate invocation for billing purposes?

Nnoskovvkirill Hi guys! Is there any plan to add a middleware support to workflows? Similar to ...

M

Matt Silverlock•5/5/25, 10:28 AM

A DB connection is alive for as long as the Workflow instance is running (short of errors or long sleep periods). I’m not sure you need middleware as we don’t function like Inngest does.

Hharisvsulaiman Does anyone have a problem when the workflow sometimes does not get the environm...

M

Matt Silverlock•5/5/25, 10:28 AM

There’s not enough info to go off here. Show your code and a reproduction.

Ttyx I am getting a very confusing bug. I am getting. `Error: (workflow.not_found) Pr...

T

tyx•5/5/25, 12:37 PM

@Matt does this seem like a system issue, or I am using things incorrectly. surprising that when run locally it works as expected and the workflow gets triggered without any errors. It's only shows up in the deployed version

Ttyx @Matt does this seem like a system issue, or I am using things incorrectly. surp...

M

Matt Silverlock•5/5/25, 12:56 PM

Does the Worker you deploy bind to it? Show your code.

Hharisvsulaiman Sure. Can I point you towards the cloudflare organisation?. This happens often. ...

M

Matt Silverlock•5/5/25, 2:03 PM

I can’t see your code unless you share a repro

MMatt Silverlock Does the Worker you deploy bind to it? Show your code.

T

tyx•5/5/25, 2:25 PM

UI shows so:
Following is my wranger.toml parts

name = "docpad-session-init"
main = "src/index.ts"
compatibility_date = "2024-10-22"
compatibility_flags = ["nodejs_compat"]

[[workflows]]
binding = "DOCPAD_SESSION_INIT"
name = "docpad-session-init"
class_name = "DocpadSessionInit"

name = "docpad-session-init"
main = "src/index.ts"
compatibility_date = "2024-10-22"
compatibility_flags = ["nodejs_compat"]

[[workflows]]
binding = "DOCPAD_SESSION_INIT"
name = "docpad-session-init"
class_name = "DocpadSessionInit"

name = "docpad-session-init"
main = "src/index.ts"
compatibility_date = "2024-10-22"
compatibility_flags = ["nodejs_compat"]

[[workflows]]
binding = "DOCPAD_SESSION_INIT"
name = "docpad-session-init"
class_name = "DocpadSessionInit"

name = "docpad-session-init"
main = "src/index.ts"
compatibility_date = "2024-10-22"
compatibility_flags = ["nodejs_compat"]

[[workflows]]
binding = "DOCPAD_SESSION_INIT"
name = "docpad-session-init"
class_name = "DocpadSessionInit"

same request made locally i get 200:
but making the same request to deployed version either through cf web ui or any other means i get hit with workflow not found.

7

7777777•5/5/25, 6:34 PM

hi all - wondering if anyone has any resources to help me get vitest working since adding

[[workflows]]

[[workflows]]

to my toml file?
I basically go the following config setup where I needed to disabled

isolatedStorage

isolatedStorage

otherwise it was complaining about not being able to find my imported Workflow class to bind.

import { defineWorkersConfig } from '@cloudflare/vitest-pool-workers/config';

export default defineWorkersConfig({
    test: {
        poolOptions: {
            workers: {
                isolatedStorage: false,
                wrangler: { configPath: './wrangler.toml' },
            },
            poolMatchGlobs: [],
        },
        maxConcurrency: 1,
    },
})

import { defineWorkersConfig } from '@cloudflare/vitest-pool-workers/config';

export default defineWorkersConfig({
    test: {
        poolOptions: {
            workers: {
                isolatedStorage: false,
                wrangler: { configPath: './wrangler.toml' },
            },
            poolMatchGlobs: [],
        },
        maxConcurrency: 1,
    },
})

import { defineWorkersConfig } from '@cloudflare/vitest-pool-workers/config';

export default defineWorkersConfig({
    test: {
        poolOptions: {
            workers: {
                isolatedStorage: false,
                wrangler: { configPath: './wrangler.toml' },
            },
            poolMatchGlobs: [],
        },
        maxConcurrency: 1,
    },
})

import { defineWorkersConfig } from '@cloudflare/vitest-pool-workers/config';

export default defineWorkersConfig({
    test: {
        poolOptions: {
            workers: {
                isolatedStorage: false,
                wrangler: { configPath: './wrangler.toml' },
            },
            poolMatchGlobs: [],
        },
        maxConcurrency: 1,
    },
})

but I'm unable to run even a simple test anymore due to

import { createExecutionContext } from "cloudflare:test";
import { describe, it, expect } from "vitest";
describe("test", () => {
  it('test', () => {
    // referencing something from cloudflare:test
    const ctx = createExecutionContext()
    expect(2).toBe(2)
  })
})

import { createExecutionContext } from "cloudflare:test";
import { describe, it, expect } from "vitest";
describe("test", () => {
  it('test', () => {
    // referencing something from cloudflare:test
    const ctx = createExecutionContext()
    expect(2).toBe(2)
  })
})

import { createExecutionContext } from "cloudflare:test";
import { describe, it, expect } from "vitest";
describe("test", () => {
  it('test', () => {
    // referencing something from cloudflare:test
    const ctx = createExecutionContext()
    expect(2).toBe(2)
  })
})

import { createExecutionContext } from "cloudflare:test";
import { describe, it, expect } from "vitest";
describe("test", () => {
  it('test', () => {
    // referencing something from cloudflare:test
    const ctx = createExecutionContext()
    expect(2).toBe(2)
  })
})

workerd/jsg/util.c++:320: error: e = kj/table.c++:49: failed: inserted row already exists in table

7

7777777•5/5/25, 6:45 PM

ah adding

singleWorkfer: true

singleWorkfer: true

got it working, so it must be that the workflows each spin up their own worker, and try to initialize something for each test?

SSakuraFC I found that the only reason that it throws (in the beginning for us) without im...

D

ddsgadget•5/5/25, 7:11 PM

right, but why can't you return an object or array? We routinely return an object or array and use it next steps. Always works. What are you supposed to return? How do you use data between steps if you can't return an array or object?

Dddsgadget right, but why can't you return an object or array? We routinely return an objec...

S

SakuraFC•5/5/25, 10:45 PM

It works for sure but it also throws an exception for some reason. The only way I found to stop the exception is to return string JSON.stringify and then use JSON.parse to turn it back to JS object/array

MMatt Silverlock A DB connection is alive for as long as the Workflow instance is running (short ...

N

noskovvkirill•5/6/25, 12:28 AM

Thanks @Matt! Is it safe do define connection outside of a step? Wouldn't it break the "Do not rely on state outside of a step" rule of Workflows?
We're connecting to our Postgres using connecting string.

const db = getDB(this.env);

const db = getDB(this.env);

Nnoskovvkirill Thanks @Matt! Is it safe do define connection outside of a step? Wouldn't it bre...

M

Matt Silverlock•5/6/25, 12:36 AM

I wouldn't consider that state - it's not data that you are trying to persist.

I would however do something like this, so that you can make sure the DB connection is alive / memoize the DB where you can:

// inside the run() method
const db: TypeOfYourDB | undefined

// inside the run() method
const db: TypeOfYourDB | undefined

// elsewhere, as a helper - e.g. on the Workflow class
async function getDB(db, this.env) {
   if (!db) {
     db = // create a new connection
   }

   return db
}

// elsewhere, as a helper - e.g. on the Workflow class
async function getDB(db, this.env) {
   if (!db) {
     db = // create a new connection
   }

   return db
}

// elsewhere, as a helper - e.g. on the Workflow class
async function getDB(db, this.env) {
   if (!db) {
     db = // create a new connection
   }

   return db
}

// elsewhere, as a helper - e.g. on the Workflow class
async function getDB(db, this.env) {
   if (!db) {
     db = // create a new connection
   }

   return db
}

SSakuraFC It works for sure but it also throws an exception for some reason. The only way ...

D

ddsgadget•5/6/25, 12:53 PM

Ah, ok, thanks very much! Will try that. Going to take some time to redo all our steps to add this everwhere. This I consider a bug, even if it was built this way that Steps can only return stringified JSON. The platform should handle that. And none of the examples show stringify and then parse, so how would anyone know to do that? https://developers.cloudflare.com/workflows/examples/send-invoices/ (we copied this example mostly for our workflows and use the {success:true} type of format.

Cloudflare Docs

Pay cart and send invoice

Send invoice when shopping cart is checked out and paid for

A

Austin B•5/6/25, 10:30 PM

I've recently built a solution on Workflows, and I'm trying to identity if I'm hitting some sort of Workers/Workflows limit or throttling. Maybe someone here can point me in the right direction.

High level summary of the solution: HTTP Worker request fires off 31 instances of one workflow. Each of those 31 fires off anywhere from 100-600 child workflows. Each of these child workflows makes a couple of Supabase calls.

Attached is a screenshot of the throughput of the worker bound to these workflows. No errors or retries occurred and the end results were what I expected. However, I don't understand the dramatic drop in throughput. Is there a way to see for sure if some service limit is being hit? (I'm on Workers Paid plan)

AAustin B I've recently built a solution on Workflows, and I'm trying to identity if I'm h...

M

Matt Silverlock•5/7/25, 12:57 AM

If you’re firing off 31 requests that each trigger hundreds of Workflows - you’re likely hitting rate limits: https://developers.cloudflare.com/workflows/reference/limits/

Cloudflare Docs

Limits

Limits that apply to authoring, deploying, and running Workflows are detailed below.

M

Matt Silverlock•5/7/25, 12:57 AM

(Sounds like a lot more than 450 per 10s)

A

Austin B•5/7/25, 2:46 AM

@Matt Silverlock I'm not sure which specific limit you're referring to, but as far as the workflow instance creation itself, I think I'm in the clear. I'm using

createBatch

createBatch

to do 100 at a time within each of the initial 31. The total amount gets queued up very quickly. The graph above is the steps processing inside those from my understanding.

I don't see anything about 450 per 10s in the link you mentioned. I've looked through the docs for Workers limits and Workflows limits, and nothing is standing out to me as obvious that my setup would be hitting. Admittedly, I'm not sure my understanding of subrequests and how steps within workflows translate to the workers limits is totally correct.

I was hoping to see some evidence within CloudFlare's dashboard itself as to what is being limited. But I can't find any errors or metrics indicating what limit might be getting hit.

AAustin B @Matt Silverlock I'm not sure which specific limit you're referring to, but as f...

M

Matt Silverlock•5/7/25, 2:50 AM

Sorry, I mean 100 / sec. 31 x 100 per request within a few seconds exceeds that? If not, can you expand on your creation rate? 31 requests over what period? Why 31?

A

Austin B•5/7/25, 2:54 AM

@Matt Silverlock 31 is arbitrary and data driven. Iterating over some entities and firing off workflows for related child entities. My understanding is that a single createBatch only counts as 1 request towards the rate limit. I'm getting this from these docs: https://developers.cloudflare.com/workflows/build/workers-api/#createbatch

So each of those 31 is not doing more than 7 createBatch calls (each batch with up to 100). Unless I'm misinterpreting the docs, this seems well within that limit. Also to be clear I'm not seeing issues with the workflow instances being created slowly. It is once they are actually queued, how quickly they get processed. The chart I showed above is not workflow instance creation

AAustin B @Matt Silverlock 31 is arbitrary and data driven. Iterating over some entities a...

M

Matt Silverlock•5/7/25, 3:02 AM

createBatch would limit that. Are you hitting all of this from a single IP? I’d open a Support ticket as hard to dive into over Discord.

I

Isak•5/7/25, 9:58 PM

Do workflows respect smart placement?

MMatt Silverlock createBatch would limit that. Are you hitting all of this from a single IP? I’d ...

O

Ollie•5/8/25, 2:42 PM

@Matt Silverlock how long does it usually take for support tickets to be seen, my P0 one has been opened for 7 days with no response or anything

I

Ibby | Fk Israel•5/8/25, 3:36 PM

Yeah Matt. Is cloudflare looking to hire folks who will help out devs onboard or just continue loosing business ?

IIbby | Fk Israel Yeah Matt. Is cloudflare looking to hire folks who will help out devs onboard or...

M

Matt Silverlock•5/8/25, 3:46 PM

We have a thread open with Ollie here with the Eng lead for the product, so...

IIbby | Fk Israel Yeah Matt. Is cloudflare looking to hire folks who will help out devs onboard or...

O

Ollie•5/8/25, 3:48 PM

Yeah to give them credit, CF have been extremely helpful, and we are greateful that we can talk to eng leads directly

I

Ibby | Fk Israel•5/8/25, 3:48 PM

Sorry i'm just busting balls

M

Matt Silverlock•5/8/25, 3:48 PM

(To be clear, we want this fixed + faster, but hitting some rough edges that we hadn't seen from other teams/customers)

I

Ibby | Fk Israel•5/8/25, 3:50 PM

Tbh; I'm trynna deploy my Nextjs app on cloudflare workers, migrating from vercel.
Tried using the opennextjs-cloudflare but running into build errors, not sure if you guys can help out.

I

Ibby | Fk Israel•5/8/25, 3:51 PM

general-helpMigrate From Vercel - NextJS App Router + API's

J

juanferreras•5/8/25, 11:27 PM

any inherit incompatibility between Workers Rate Limiting e.g.

ratelimit

ratelimit

and a workflow worker?

[[unsafe.bindings]]
name = "RATE_LIMIT_MEASUREMENT_GUEST"
type = "ratelimit"
namespace_id = "1000"
simple = { limit = 3, period = 60 }

[[unsafe.bindings]]
name = "RATE_LIMIT_MEASUREMENT_GUEST"
type = "ratelimit"
namespace_id = "1000"
simple = { limit = 3, period = 60 }

[[unsafe.bindings]]
name = "RATE_LIMIT_MEASUREMENT_GUEST"
type = "ratelimit"
namespace_id = "1000"
simple = { limit = 3, period = 60 }

[[unsafe.bindings]]
name = "RATE_LIMIT_MEASUREMENT_GUEST"
type = "ratelimit"
namespace_id = "1000"
simple = { limit = 3, period = 60 }

export default class WorkflowsService extends WorkerEntrypoint<CloudflareEnv> {
  // ...
  async createWorkflow(payload: Params) {
    // check if the user has exceeded the limit
    const RATE_LIMITER = this.env.RATE_LIMIT_MEASUREMENT_GUEST;
    const { success } = await RATE_LIMITER.limit({
      key: payload.userIdOrIpAddress,
    });
    // success locally works as expected but on production I can x3/x4 the limit and still success=true (all sending the exact same

export default class WorkflowsService extends WorkerEntrypoint<CloudflareEnv> {
  // ...
  async createWorkflow(payload: Params) {
    // check if the user has exceeded the limit
    const RATE_LIMITER = this.env.RATE_LIMIT_MEASUREMENT_GUEST;
    const { success } = await RATE_LIMITER.limit({
      key: payload.userIdOrIpAddress,
    });
    // success locally works as expected but on production I can x3/x4 the limit and still success=true (all sending the exact same

export default class WorkflowsService extends WorkerEntrypoint<CloudflareEnv> {
  // ...
  async createWorkflow(payload: Params) {
    // check if the user has exceeded the limit
    const RATE_LIMITER = this.env.RATE_LIMIT_MEASUREMENT_GUEST;
    const { success } = await RATE_LIMITER.limit({
      key: payload.userIdOrIpAddress,
    });
    // success locally works as expected but on production I can x3/x4 the limit and still success=true (all sending the exact same

export default class WorkflowsService extends WorkerEntrypoint<CloudflareEnv> {
  // ...
  async createWorkflow(payload: Params) {
    // check if the user has exceeded the limit
    const RATE_LIMITER = this.env.RATE_LIMIT_MEASUREMENT_GUEST;
    const { success } = await RATE_LIMITER.limit({
      key: payload.userIdOrIpAddress,
    });
    // success locally works as expected but on production I can x3/x4 the limit and still success=true (all sending the exact same

J

juanferreras•5/8/25, 11:31 PM

I guess if not it could be related to the workflow-consumers (two different apps, but both call it using RPC/service bindings, and they are using

smart

smart

placement)

M

Magic Greg•5/9/25, 4:38 PM

hello - is there a way to terminate or restart a workflow right now?

MMagic Greg hello - is there a way to terminate or restart a workflow right now?

M

Matt Silverlock•5/9/25, 6:23 PM

https://developers.cloudflare.com/workflows/build/workers-api/#terminate

Cloudflare Docs

Workers API

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

MMatt Silverlock https://developers.cloudflare.com/workflows/build/workers-api/#terminate

M

Magic Greg•5/9/25, 6:54 PM

Have you tried it? It says it’s not yet implemented when I try it.

森

森@VerseLink (RW)•5/9/25, 8:17 PM

does the waitForEvent count towards the workflow concurrent limit?

J

jason•5/10/25, 7:44 PM

Request for better error messages on workflow runs.

I see constant error messages (red status) on my workflow runs, even when all steps have worked successfully as I expected of them, but the status message doesn't help me know why.

In an effort to get rid of all these red status, I've stripped my workflow down to the bare minimum, and tried over and over...but still get the error in 95% of cases. I'm starting to conclude it's just Workflows being flaky for the end result status and not surfacing a useful error message:

    // Something in one of these two steps causes the workflow to show outcome of "exception" and
    // level of "error". What?
    const { foo, bar } = await step.do("test", async () => {
      const foo = "hello";
      const bar = "world";
      return {
        foo,
        bar,
      };
    });
    await step.do("test", async () => {
      return foo + bar;
    });

    // This will not cause an error...most the time...when it's the *only* step in the workflow.
    await step.do("test", async () => {
      return "foooo";
    });

    // Something in one of these two steps causes the workflow to show outcome of "exception" and
    // level of "error". What?
    const { foo, bar } = await step.do("test", async () => {
      const foo = "hello";
      const bar = "world";
      return {
        foo,
        bar,
      };
    });
    await step.do("test", async () => {
      return foo + bar;
    });

    // This will not cause an error...most the time...when it's the *only* step in the workflow.
    await step.do("test", async () => {
      return "foooo";
    });

    // Something in one of these two steps causes the workflow to show outcome of "exception" and
    // level of "error". What?
    const { foo, bar } = await step.do("test", async () => {
      const foo = "hello";
      const bar = "world";
      return {
        foo,
        bar,
      };
    });
    await step.do("test", async () => {
      return foo + bar;
    });

    // This will not cause an error...most the time...when it's the *only* step in the workflow.
    await step.do("test", async () => {
      return "foooo";
    });

    // Something in one of these two steps causes the workflow to show outcome of "exception" and
    // level of "error". What?
    const { foo, bar } = await step.do("test", async () => {
      const foo = "hello";
      const bar = "world";
      return {
        foo,
        bar,
      };
    });
    await step.do("test", async () => {
      return foo + bar;
    });

    // This will not cause an error...most the time...when it's the *only* step in the workflow.
    await step.do("test", async () => {
      return "foooo";
    });

Here is an example request ID that gives an error status for the above steps inside a workflow: IQI88BKIF6L9BMLR

Anybody else seeing this or know what's going on?

森

森@VerseLink (RW)•5/10/25, 10:26 PM

when i run workflow locally, occasionally i get this error

workerd/jsg/setup.c++:39: fatal: V8 fatal error; location = :0; message = Missing deoptimization information for OptimizedJSFrame::Summarize.

workerd/jsg/setup.c++:39: fatal: V8 fatal error; location = :0; message = Missing deoptimization information for OptimizedJSFrame::Summarize.

and it just crashes the runtime outright (the command shell would be working), but no http requests can be proccessed

Pretty sure Workflows is built off of Queues. So read docs of both and weigh up pros and cons of you

Similar Threads

Similar Threads

Similar Threads