To keep you posted, the bug has been identified and will be rolling out throughout next week probabl

L

Luke•1/31/25, 7:27 PM

Is there an easy way to debug workflows in vs code? In my workers project I can just use the

javascript debug terminal

javascript debug terminal

javascript debug terminal

javascript debug terminal and it works fine. For some reason it doesn't w/ workflows - all of my breakpoints are "unbound"

LLuke Is there an easy way to debug workflows in vs code? In my workers project I can ...

L

Luke•1/31/25, 7:35 PM

Disregard - i forgot that w/ workers I don't use the

javascript debug terminal

javascript debug terminal

javascript debug terminal

javascript debug terminal I have to run

wrangler dev

wrangler dev

and then attach vs code to the process. The same works fine w/ workflows.

L

Luke•1/31/25, 7:36 PM

Next question I have is - how can I restart a failed workflow? I tried using

instance.restart

instance.restart

instance.restart

instance.restart,

instance.terminate

instance.terminate

instance.terminate

instance.terminate, etc. and it says

Not implemented yet

Not implemented yet

Not implemented yet

Not implemented yet. Any tips on that?

Kkchro3 Hi folks, we're seeing that if you execute a sleep step, it takes a few minutes ...

S

SeekerdasbatatasOP•1/31/25, 7:58 PM

It's an implementation detail for workflows - we need to allow some time for top level work, this time might get reduced before GA, but for beta we were more generous because of correctness (because it's JS, you can do some really weird stuff with control flow in a relatively easy way

)

S

SeekerdasbatatasOP•1/31/25, 7:59 PM

We hopefully are

a bunch of stuff next week that will make the queuing aspect better :soontm:

L

Luke•2/1/25, 6:10 AM

I'm trying to use Browser Rendering in my workflow but debug the code because:

I can't run browser rendering locally (need to use
```
--remote
```
```
--remote
```
)
I can't run workflows using using
```
--remote
```
```
--remote
```

Any good work around for this? I'm trying to avoid having multiple projects like pushing to a queue to have have Browser Rendering pick it up and process it. It feels like a perfect synergy for Workflows to work with Browser Rendering but the development lifecycle might be too painful at the moment to need to debug via deploying the code and using

console.log

console.log

s

C

crunchy•2/1/25, 10:46 PM

By the way, workflows do not trigger for me locallly (dev) when created by worker. Works in prod. wrangler 3.107.2

C

crunchy•2/1/25, 10:47 PM

Also what sort of concurrency is likely to be allowed in future, are these things intended for use at scale?

D

Dæ•2/1/25, 11:44 PM

Can someone give me an intro to this… I’ll ask ChatGPT

A

Ashkan•2/1/25, 11:49 PM

guys how can I get access to env variable in workflow?

A

Ashkan•2/1/25, 11:50 PM

export class myclass extends WorkflowEntrypoint<Env, Params> {
    async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
    
    }
}

export class myclass extends WorkflowEntrypoint<Env, Params> {
    async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
    
    }
}

export class myclass extends WorkflowEntrypoint<Env, Params> {
    async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
    
    }
}

export class myclass extends WorkflowEntrypoint<Env, Params> {
    async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
    
    }
}

AAshkan `export class myclass extends WorkflowEntrypoint<Env, Params> { async run(ev...

A

Ashkan•2/1/25, 11:52 PM

I found it as a comment in example code:

// Can access bindings on this.env

// Can access bindings on this.env

// Can access bindings on this.env

// Can access bindings on this.env

F

Fernando Barroso•2/2/25, 1:27 AM

two questions:

1) Is there an architectural icon for cf workflows yet?
2) anybody know where can I get a library of icons that I could use to build diagrams like these:

FFernando Barroso two questions: 1) Is there an architectural icon for cf workflows yet? 2) anybo...

I

Isaac McFadyen•2/2/25, 1:48 AM

For 2) see https://cfdata.lol/icons/ (unofficial)

I

Isaac McFadyen•2/2/25, 1:48 AM

Not sure about 1.

F

Fernando Barroso•2/2/25, 2:24 AM

Oh that site is pretty sick - thank you!

A

apolodoro•2/2/25, 12:14 PM

Is there a way to limit concurrent workflows based on their id? For example if the id starts with 'type1' only one workflow can be running at the same time

Aapolodoro Is there a way to limit concurrent workflows based on their id? For example if t...

M

Matt Silverlock•2/2/25, 2:41 PM

Not yet. Looking at controls here by Workflow - e.g. a

max_concurrent_instances

max_concurrent_instances

max_concurrent_instances

max_concurrent_instances config.

Ccrunchy Also what sort of concurrency is likely to be allowed in future, are these thing...

M

Matt Silverlock•2/2/25, 2:42 PM

Next big step is 4,500 concurrent (very soon) and we want to get to 10k (at least) over the next few weeks/this quarter.

Making sure it all works + nothing bottlenecks.

MMatt Silverlock Not yet. Looking at controls here by Workflow - e.g. a `max_concurrent_instances...

A

apolodoro•2/2/25, 2:56 PM

Nice but not yet implemented right?

Aapolodoro Nice but not yet implemented right?

S

SeekerdasbatatasOP•2/3/25, 11:53 AM

correct

SSeekerdasbatatas correct

J

Jadugar_Jaggu•2/3/25, 4:13 PM

Can I know the limit of memory per workflow ?

For workers it's 128 MB shared per invocation right?

JJadugar_Jaggu Can I know the limit of memory per workflow ? For workers it's 128 MB shared p...

S

SeekerdasbatatasOP•2/3/25, 4:15 PM

it's the same 128MiB on Workflows too (and depending on scheduling, it maybe be shared with other instances)

SSeekerdasbatatas it's the same 128MiB on Workflows too (and depending on scheduling, it maybe be ...

J

Jadugar_Jaggu•2/3/25, 4:16 PM

Ok it means every step will get 128 MiB or a whole workerflow ?

JJadugar_Jaggu Ok it means every step will get 128 MiB or a whole workerflow ?

S

SeekerdasbatatasOP•2/3/25, 4:17 PM

the whole workflow

SSeekerdasbatatas the whole workflow

J

Jadugar_Jaggu•2/3/25, 4:20 PM

Ok thanks, well this is somewhat concerning if there are some tasks which use memory too much.

That's why may be my workflow steps are throwing an error of cpu/memory limit after doing work of around 128 MiB ( nearly )

But on retry it's again working till 128 MiB

what's this behaviour?

D

D Trombett•2/3/25, 6:07 PM

Docs say

step.sleep

step.sleep

step.sleep

step.sleep duration is in seconds if it's a number but it seems to me that it's actually ms?

D

D Trombett•2/3/25, 7:26 PM

ah I see, thanks

V

Victor•2/4/25, 9:44 AM

I'm unable to use cross-script calls to workflows with wrangler dev (local)

Getting

Worker "workflows:AfterContractActivated-development"'s binding "USER_WORKFLOW" refers to a service "core:user:delivery-development", but no such service is defined.

Worker "workflows:AfterContractActivated-development"'s binding "USER_WORKFLOW" refers to a service "core:user:delivery-development", but no such service is defined.

Worker "workflows:AfterContractActivated-development"'s binding "USER_WORKFLOW" refers to a service "core:user:delivery-development", but no such service is defined.

Worker "workflows:AfterContractActivated-development"'s binding "USER_WORKFLOW" refers to a service "core:user:delivery-development", but no such service is defined.

Is that not supported? It doesn't seem specified in the docs

L

laurynas•2/4/25, 1:31 PM

has there been any discussion on setting error callbacks for workflow steps? I’d love an

onError

onError

onError

onError callback i could pass where i could set some custom logic to try when a step errors. E.g.:

export class TextGenerator extends WorkflowEntrypoint<CloudflareBindings> {
  async run(
    event: Readonly<WorkflowEvent<{ prompt: string }>>,
    step: WorkflowStep,
  ) {
    const { prompt } = event.payload;

    return await step.do(
      "generate-text",
      {
        retries: { limit: 3, delay: 1000, backoff: "exponential" },
        onError: async (error, retry) => {
          if (error instanceof AITimeoutError) {
            // Complex model timed out, try with a faster one first
            try {
              return await generateText({
                model: "gpt-3.5-turbo",
                prompt,
                timeout: 5000,
              });
            } catch {
              // If faster model fails, retry with original complex model (retry is the original callback in step.do)
              return retry();
            }
          }
          throw error;
        }
      },

export class TextGenerator extends WorkflowEntrypoint<CloudflareBindings> {
  async run(
    event: Readonly<WorkflowEvent<{ prompt: string }>>,
    step: WorkflowStep,
  ) {
    const { prompt } = event.payload;

    return await step.do(
      "generate-text",
      {
        retries: { limit: 3, delay: 1000, backoff: "exponential" },
        onError: async (error, retry) => {
          if (error instanceof AITimeoutError) {
            // Complex model timed out, try with a faster one first
            try {
              return await generateText({
                model: "gpt-3.5-turbo",
                prompt,
                timeout: 5000,
              });
            } catch {
              // If faster model fails, retry with original complex model (retry is the original callback in step.do)
              return retry();
            }
          }
          throw error;
        }
      },

export class TextGenerator extends WorkflowEntrypoint<CloudflareBindings> {
  async run(
    event: Readonly<WorkflowEvent<{ prompt: string }>>,
    step: WorkflowStep,
  ) {
    const { prompt } = event.payload;

    return await step.do(
      "generate-text",
      {
        retries: { limit: 3, delay: 1000, backoff: "exponential" },
        onError: async (error, retry) => {
          if (error instanceof AITimeoutError) {
            // Complex model timed out, try with a faster one first
            try {
              return await generateText({
                model: "gpt-3.5-turbo",
                prompt,
                timeout: 5000,
              });
            } catch {
              // If faster model fails, retry with original complex model (retry is the original callback in step.do)
              return retry();
            }
          }
          throw error;
        }
      },

export class TextGenerator extends WorkflowEntrypoint<CloudflareBindings> {
  async run(
    event: Readonly<WorkflowEvent<{ prompt: string }>>,
    step: WorkflowStep,
  ) {
    const { prompt } = event.payload;

    return await step.do(
      "generate-text",
      {
        retries: { limit: 3, delay: 1000, backoff: "exponential" },
        onError: async (error, retry) => {
          if (error instanceof AITimeoutError) {
            // Complex model timed out, try with a faster one first
            try {
              return await generateText({
                model: "gpt-3.5-turbo",
                prompt,
                timeout: 5000,
              });
            } catch {
              // If faster model fails, retry with original complex model (retry is the original callback in step.do)
              return retry();
            }
          }
          throw error;
        }
      },

Llaurynas has there been any discussion on setting error callbacks for workflow steps? I’d...

M

Matt Silverlock•2/4/25, 4:46 PM

Isn’t that just another step? Write an outer step that encapsulates both.

Any

onError

onError

onError

onError callback would still have to be treated like another step, but ends up being another not-quite-a-step API with its own semantics.

Run stepA, catch the error, call optional stepB, etc.

D

Dom•2/5/25, 4:10 AM

Hello!
I'm working on my first workflow. Its supposed to send a couple of emails via Resend.
The workflow itself works.

But I want to call it from a Pages project.

In my wrangler.jsonc I have:

  "services": [
    {
      "binding": "WORKFLOW_SERVICE",
      "service": "wf-portcity-ai"
    }
  ],

  "services": [
    {
      "binding": "WORKFLOW_SERVICE",
      "service": "wf-portcity-ai"
    }
  ],

  "services": [
    {
      "binding": "WORKFLOW_SERVICE",
      "service": "wf-portcity-ai"
    }
  ],

  "services": [
    {
      "binding": "WORKFLOW_SERVICE",
      "service": "wf-portcity-ai"
    }
  ],

But what should I type the

WORKFLOW_SERVICE

WORKFLOW_SERVICE

WORKFLOW_SERVICE

WORKFLOW_SERVICE Env variabe as?
And how do I trigger my workflow?

D

Dom•2/5/25, 4:37 AM

https://developers.cloudflare.com/workflows/build/call-workflows-from-pages/

This would really benefit from a complete source example

Cloudflare Docs

Call Workflows from Pages · Cloudflare Workflows docs

You can bind and trigger Workflows from Pages Functions by deploying a Workers project with your Workflow definition and then invoking that Worker using service bindings or a standard fetch() call.

D

Dom•2/5/25, 4:45 AM

Whatever I seem to do - I always get:

✘ [ERROR] TypeError: The RPC receiver does not implement the method "createInstance"

✘ [ERROR] TypeError: The RPC receiver does not implement the method "createInstance"

✘ [ERROR] TypeError: The RPC receiver does not implement the method "createInstance"

✘ [ERROR] TypeError: The RPC receiver does not implement the method "createInstance"

Nnil Alternatively.. if that breaks rules of global state.. wondering if this works? ...

S

SeekerdasbatatasOP•2/5/25, 10:42 AM

that could work, but

yieldEvent

yieldEvent

yieldEvent

yieldEvent is outside of a step - meaning that these calls can be repeated multiple times (not sure if that's you want or not)

SSushidata Hi all, day 2 now of not being able to access Workflows 😦

M

Matt Silverlock•2/5/25, 6:18 PM

Can you clear all of your cookies? cc @Diogo Ferreira

DDom Whatever I seem to do - I always get: `✘ [ERROR] TypeError: The RPC receiver doe...

M

Matt Silverlock•2/5/25, 6:19 PM

Can you share your code?

MMatt Silverlock Can you clear all of your cookies? cc @Diogo Ferreira

V

Victor•2/5/25, 6:20 PM

https://discord.com/channels/595317990191398933/1299119533319131209/1336492428353474601

Nnil The motivation is when you do workflows, you would want to incrementally update ...

F

Focux•2/5/25, 6:26 PM

It'd be cool if you could update some state from within a workflow and then be able to access that state by calling the workflow binding from a worker

F

Focux•2/5/25, 6:26 PM

I guess you can implement this on userland, but it'd be cool if it was built-in

T

Teddy•2/5/25, 9:52 PM

Hi

I'm following the RAGWorkflow tutorial in the docs, and somehow I'm getting an

internal error

internal error

before the workflow tries to execute any steps. Any ideas?

export class RAGWorkflow {
    async run(event, step) {
        const { text } = event.params;

        const record = await step.do('create database record', async () => {
            const query = 'INSERT INTO notes (text) VALUES (?) RETURNING *';

            const { results } = await  env.DB.prepare(query).bind(text).run();

            const record = results[0];
            if (!record) throw new Error('Failed to create note');
            return record;
        });

        const embedding = await step.do('generate embedding', async () => {
            const embeddings = await env.AI.run('@cf/baai/bge-base-en-v1.5', { text: text });
            const values = embeddings.data[0];
            if (!values) throw new Error('Failed to generate vector embedding');
            return values;
        });

        await step.do('insert vector', async () => {
            return env.VECTOR_INDEX.upsert([
                {
                    id: record.id.toString(),
                    values: embedding,
                },
            ]);
        });
    }
}

export class RAGWorkflow {
    async run(event, step) {
        const { text } = event.params;

        const record = await step.do('create database record', async () => {
            const query = 'INSERT INTO notes (text) VALUES (?) RETURNING *';

            const { results } = await  env.DB.prepare(query).bind(text).run();

            const record = results[0];
            if (!record) throw new Error('Failed to create note');
            return record;
        });

        const embedding = await step.do('generate embedding', async () => {
            const embeddings = await env.AI.run('@cf/baai/bge-base-en-v1.5', { text: text });
            const values = embeddings.data[0];
            if (!values) throw new Error('Failed to generate vector embedding');
            return values;
        });

        await step.do('insert vector', async () => {
            return env.VECTOR_INDEX.upsert([
                {
                    id: record.id.toString(),
                    values: embedding,
                },
            ]);
        });
    }
}

export class RAGWorkflow {
    async run(event, step) {
        const { text } = event.params;

        const record = await step.do('create database record', async () => {
            const query = 'INSERT INTO notes (text) VALUES (?) RETURNING *';

            const { results } = await  env.DB.prepare(query).bind(text).run();

            const record = results[0];
            if (!record) throw new Error('Failed to create note');
            return record;
        });

        const embedding = await step.do('generate embedding', async () => {
            const embeddings = await env.AI.run('@cf/baai/bge-base-en-v1.5', { text: text });
            const values = embeddings.data[0];
            if (!values) throw new Error('Failed to generate vector embedding');
            return values;
        });

        await step.do('insert vector', async () => {
            return env.VECTOR_INDEX.upsert([
                {
                    id: record.id.toString(),
                    values: embedding,
                },
            ]);
        });
    }
}

export class RAGWorkflow {
    async run(event, step) {
        const { text } = event.params;

        const record = await step.do('create database record', async () => {
            const query = 'INSERT INTO notes (text) VALUES (?) RETURNING *';

            const { results } = await  env.DB.prepare(query).bind(text).run();

            const record = results[0];
            if (!record) throw new Error('Failed to create note');
            return record;
        });

        const embedding = await step.do('generate embedding', async () => {
            const embeddings = await env.AI.run('@cf/baai/bge-base-en-v1.5', { text: text });
            const values = embeddings.data[0];
            if (!values) throw new Error('Failed to generate vector embedding');
            return values;
        });

        await step.do('insert vector', async () => {
            return env.VECTOR_INDEX.upsert([
                {
                    id: record.id.toString(),
                    values: embedding,
                },
            ]);
        });
    }
}

T

Teddy•2/5/25, 9:54 PM

To keep you posted, the bug has been identified and will be rolling out throughout next week probabl

Similar Threads

Similar Threads

Similar Threads