had the same issue. hope they fix this. I think this is just a bug where the queued state cannot be

T

tornado•12/2/24, 9:57 PM

The limits page say that the 30 second cpu limit is per step but it seems like the cpu time is actually for the workflow.

D

ddsgadgetOP•12/2/24, 9:57 PM

Do you have any ETA when the workflows will be out of beta? Just worried about potential changes and the need to refactor. Not sure how much really changes between beta and when it is out of beta. I've never used a Cloudflare beta product before...But really love workflows. Makes so many thing easier.

Kkingmesal Does a single workflow instantiation inherit the subrequests limit defined in wo...

M

Matt Silverlock•12/2/24, 10:31 PM

Yes.

Dddsgadget Do you have any ETA when the workflows will be out of beta? Just worried about p...

M

Matt Silverlock•12/2/24, 10:31 PM

We're still very early on - it won't be this year / Jan. Quality > time.

T

tornado•12/3/24, 4:12 PM

Is there a clear explanation of how cpu limit works? I'm hitting cpu limit in the workflow even though previously the individual steps logic was well within the cpu limit. It seems like the workflow cpu limit is the sum of the steps cpu usage. Also I have a large try, catch to eventually cleanup but it when I get the CPU exceeded error, the last step never runs

T

tornado•12/3/24, 4:50 PM

Is there a difference between using Promise.all and having a for loop that adds the step output to an array? The array will still be comprised of only step.do returns so that should be fine right?

T

tornado•12/3/24, 5:37 PM

Please help, my workflow is crashing and not continuing to next steps due to CPU limit exceeded but I do everything inside steps, there is virtually no work done in the workflow itself.

Ttornado Is there a clear explanation of how cpu limit works? I'm hitting cpu limit in th...

V

Victor•12/3/24, 5:41 PM

https://developers.cloudflare.com/workers/platform/limits/#cpu-time how it's calculated

Cloudflare Docs

Limits · Cloudflare Workers docs

Cloudflare Workers plan and platform limits.

Ttornado Please help, my workflow is crashing and not continuing to next steps due to CPU...

V

Victor•12/3/24, 5:43 PM

https://developers.cloudflare.com/workflows/reference/limits/ total cpu time of workflow is unlimited, but per step (listed as

Compute time per step

Compute time per step

Compute time per step

Compute time per step) you have 10 seconds (free plan) or 30 seconds (paid plan)

Cloudflare Docs

Limits · Cloudflare Workflows docs

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

T

tornado•12/3/24, 6:13 PM

Can the return of a step be an instantiated class object or will that cause problems if the workflow restarts at some point?

森

森@VerseLink (RW)•12/4/24, 12:22 AM

Can someone confirm if durable objects never gets evicted if it creates a workflow instance? Will I be billed for durations in DO?

森

森@VerseLink (RW)•12/4/24, 12:25 AM

I tried creating an empty DO and have it invoke a workflow that simply sleeps for 30seconds.

The duration should be enough to evict a DO under normal circumstances, however, when the DO is called from the workflow again (via this.env binding), the DO's constructor was never ran again indicating that the instance never got evicted.

MMatt Silverlock Yes.

I

inaridiy•12/4/24, 6:12 AM

Is there a good way to alleviate this limitation?
In the meantime, I am going to try the method of calling a child Workflow from a Workflow.

森森@VerseLink (RW)I tried creating an empty DO and have it invoke a workflow that simply sleeps fo...

M

Matt Silverlock•12/4/24, 8:52 AM

There’s no guarantee that a DO will be slept right on 30 seconds. Try longer. If you need to keep a DO running, use an Alarm. You will (necessarily) pay for the duration.

N

nixology•12/4/24, 9:16 AM

Played a little with workflows, its very good & useful. Just wondering, I couldn't figure out if I want to use CF Workflows to hook it up to build a workflow builder tool, where user can drag nodes to create a workflow. How to do so? As of now it doesn't seem possible as each step needs to be statically defined.

Nnixology Played a little with workflows, its very good & useful. Just wondering, I couldn...

M

makrdev•12/4/24, 11:46 AM

You can dynamically create steps with an array of objects (config for each step).

Nnixology Played a little with workflows, its very good & useful. Just wondering, I couldn...

M

Matt Silverlock•12/4/24, 12:57 PM

Some folks are already doing that. You don’t need to define steps statically. It’s just code. Create them conditionally, import them, etc. If your run() method calls them, it works.

MMatt Silverlock Some folks are already doing that. You don’t need to define steps statically. It...

M

Matt Silverlock•12/4/24, 12:58 PM

https://x.com/burcs/status/1859669872814457108?s=46&t=-b_yqYsCDhhJwbouT5Ht6g

brandon (@burcs) on X

have been playing around with an idea on top of cloudflare's new workflows...

excited to share it soon – it's truly game changing

Twitter

•

11/21/24, 6:47 PM

T

telliks•12/4/24, 2:18 PM

Is there a deadletter "queue" equivalent for workflows/workflow steps? Ie. I want to know when a step stopped retrying so I can manually intervene.

W

Warren•12/4/24, 2:35 PM

I am trying to invoke a Cloudflare Workflow via RPC from a different Worker. this workflow is created as intended, but I want the invoker to receive the id so as to do stuff with the workflow. these are my methods:

export default {
  async fetch(): Promise<Response> {
    // Return 400 for direct HTTP requests since workflows should be triggered via bindings
    return Response.json(
      { error: "Workflows must be triggered via bindings" },
      { status: 400 },
    );
  },
  async create({ params }: { params: InitSyncParams }, env: Env) {
    const workflow = await env.SYNC_REPO_INIT_WORKFLOW.create({ params });
    return workflow.id;
  },
  async terminate(id: string, env: Env) {
    const instance = await env.SYNC_REPO_INIT_WORKFLOW.get(id);
    await instance.terminate();
  },
  async getInstanceStatus(id: string, env: Env) {
    const instance = await env.SYNC_REPO_INIT_WORKFLOW.get(id);
    return await instance.status();
  },
};

export default {
  async fetch(): Promise<Response> {
    // Return 400 for direct HTTP requests since workflows should be triggered via bindings
    return Response.json(
      { error: "Workflows must be triggered via bindings" },
      { status: 400 },
    );
  },
  async create({ params }: { params: InitSyncParams }, env: Env) {
    const workflow = await env.SYNC_REPO_INIT_WORKFLOW.create({ params });
    return workflow.id;
  },
  async terminate(id: string, env: Env) {
    const instance = await env.SYNC_REPO_INIT_WORKFLOW.get(id);
    await instance.terminate();
  },
  async getInstanceStatus(id: string, env: Env) {
    const instance = await env.SYNC_REPO_INIT_WORKFLOW.get(id);
    return await instance.status();
  },
};

export default {
  async fetch(): Promise<Response> {
    // Return 400 for direct HTTP requests since workflows should be triggered via bindings
    return Response.json(
      { error: "Workflows must be triggered via bindings" },
      { status: 400 },
    );
  },
  async create({ params }: { params: InitSyncParams }, env: Env) {
    const workflow = await env.SYNC_REPO_INIT_WORKFLOW.create({ params });
    return workflow.id;
  },
  async terminate(id: string, env: Env) {
    const instance = await env.SYNC_REPO_INIT_WORKFLOW.get(id);
    await instance.terminate();
  },
  async getInstanceStatus(id: string, env: Env) {
    const instance = await env.SYNC_REPO_INIT_WORKFLOW.get(id);
    return await instance.status();
  },
};

export default {
  async fetch(): Promise<Response> {
    // Return 400 for direct HTTP requests since workflows should be triggered via bindings
    return Response.json(
      { error: "Workflows must be triggered via bindings" },
      { status: 400 },
    );
  },
  async create({ params }: { params: InitSyncParams }, env: Env) {
    const workflow = await env.SYNC_REPO_INIT_WORKFLOW.create({ params });
    return workflow.id;
  },
  async terminate(id: string, env: Env) {
    const instance = await env.SYNC_REPO_INIT_WORKFLOW.get(id);
    await instance.terminate();
  },
  async getInstanceStatus(id: string, env: Env) {
    const instance = await env.SYNC_REPO_INIT_WORKFLOW.get(id);
    return await instance.status();
  },
};

unfortunately, when I'm trying to get

.id

.id

, I get the following error message:

Error: AssertionError: Could not retrieve instance metadata

Error: AssertionError: Could not retrieve instance metadata

Error: AssertionError: Could not retrieve instance metadata

Error: AssertionError: Could not retrieve instance metadata.

would appreciate any help. prefer using the JavaScript RPC as that would mean I don't have to implement any auth layer or try to figure out how to programmtically link the URL of my Workers

WWarren I am trying to invoke a Cloudflare Workflow via RPC from a different Worker. thi...

M

Matt Silverlock•12/4/24, 2:50 PM

Is this in prod? Local dev? What version of wrangler?

S

skip•12/5/24, 2:06 AM

Is there a way to trigger another workflow then pause until it completes and recieve the output JSON directly?

MMatt Silverlock https://x.com/burcs/status/1859669872814457108?s=46&t=-b_yqYsCDhhJwbouT5Ht6g

M

makrdev•12/5/24, 11:03 AM

Can we create workflows with workers for platforms?

Mmakrdev Can we create workflows with workers for platforms?

M

Matt Silverlock•12/5/24, 11:06 AM

You can’t accept user-created scripts as Workflows that your WfP dispatcher calls, if that’s what you’re asking.

MMatt Silverlock You can’t accept user-created scripts as Workflows that your WfP dispatcher call...

M

makrdev•12/5/24, 11:09 AM

What if I create the initial workflow definition and run dynamic steps? Im trying to give each tenant its own instance with separate limits.

Mmakrdev What if I create the initial workflow definition and run dynamic steps? Im tryin...

M

Matt Silverlock•12/5/24, 11:11 AM

You can run whatever code you like: you specifically asked about WfP. If users aren’t writing any code then I wouldn’t call that WfP.

If they (untrusted users) are supplying code, then you’ll want WfP.

Sskip Is there a way to trigger another workflow then pause until it completes and rec...

S

skip•12/5/24, 11:12 AM

So, sort of like making a DO step that forks to another seperate workflow

MMatt Silverlock You can run whatever code you like: you specifically asked about WfP. If users a...

M

makrdev•12/5/24, 11:15 AM

Maybe I explained in a wrong way. Basically what I want to achieve is deploying separate worker for each tenant with a pre-defined workflow ( I assume they have separate concurrency limits etc.) and running dynamic workflows with a config(created by a no-code app you shared as an example)

Sskip Is there a way to trigger another workflow then pause until it completes and rec...

D

DeChill•12/5/24, 11:30 AM

I'm looking for something similar. I cannot find a way to get the "Workflow" output. It is shown in the Portal after the Worfklow finished, but

await instance.status()

await instance.status()

only gets me an array of the output from the individual steps. Not the final Worfklow return value.

F

Focux•12/5/24, 3:59 PM

@skip i asked that some days ago, and currently, you can't. they said they will take the feedback into account

F

Focux•12/5/24, 3:59 PM

workflows

F

Focux•12/5/24, 4:01 PM

i wish there were a public roadmap or some way to add/upvote feature requests

D

DeChill•12/5/24, 6:22 PM

How would I programmatically get the Workflow

Output

Output

? Is it only available via the GraphQL API?

DDeChill How would I programmatically get the Workflow `Output`? Is it only available via...

S

Seekerdasbatatas•12/5/24, 9:52 PM

You can get it from api.cloudflare.com (sorry I'm on the phone)

S

Seekerdasbatatas•12/5/24, 9:52 PM

Or via the binding

SSeekerdasbatatas Or via the binding

D

DeChill•12/5/24, 9:59 PM

Thanks for the reply, but how can I get it via the binding?

await instance.status()

await instance.status()

only gives me the output of the steps inside the workflow, not the workflow return value.

DDeChill Thanks for the reply, but how can I get it via the binding? `await instance.stat...

F

Focux•12/5/24, 10:42 PM

await instance.status().output

await instance.status().output

FFocux `await instance.status().output`

I

Isaac McFadyen•12/5/24, 10:48 PM

^ but you'll need brackets around it because the promise is the

status()

status()

not the

output

output

, so

(await instance.status()).output

(await instance.status()).output

FFocux `await instance.status().output`

D

DeChill•12/5/24, 11:47 PM

I'm reading the output value, but as I wrote in my message, the

output

output

property of the

InstanceStatus

InstanceStatus

does not contain the Workflow return value, even when the workflow is completed. I'm only seeing an array of the outputs from the individual steps called inside the workflow.

O

oof2win2•12/5/24, 11:51 PM

would this be valid workflows code? everything is deterministic as all results are computed from steps, and i just await them all at the end

const generateTitleStep = step.do(
  "Generate the project title",
  async () => {
    console.log("Generate the project title");
    const anthropic = createAnthropic({
      apiKey: this.env.ANTHROPIC_API_KEY,
    });

    return {};
  },
);
const generateNotesStep = step.do(
  "Generate the project notes",
  async () => {
    console.log("Generate the project notes");
    return {};
  },
);
// option A
await step.do("Await all project generation steps", async () => {
  await generateTitleStep;
  await generateNotesStep;
});
// option B
await Promise.all([generateTitleStep, generateNotesStep]);

const generateTitleStep = step.do(
  "Generate the project title",
  async () => {
    console.log("Generate the project title");
    const anthropic = createAnthropic({
      apiKey: this.env.ANTHROPIC_API_KEY,
    });

    return {};
  },
);
const generateNotesStep = step.do(
  "Generate the project notes",
  async () => {
    console.log("Generate the project notes");
    return {};
  },
);
// option A
await step.do("Await all project generation steps", async () => {
  await generateTitleStep;
  await generateNotesStep;
});
// option B
await Promise.all([generateTitleStep, generateNotesStep]);

const generateTitleStep = step.do(
  "Generate the project title",
  async () => {
    console.log("Generate the project title");
    const anthropic = createAnthropic({
      apiKey: this.env.ANTHROPIC_API_KEY,
    });

    return {};
  },
);
const generateNotesStep = step.do(
  "Generate the project notes",
  async () => {
    console.log("Generate the project notes");
    return {};
  },
);
// option A
await step.do("Await all project generation steps", async () => {
  await generateTitleStep;
  await generateNotesStep;
});
// option B
await Promise.all([generateTitleStep, generateNotesStep]);

const generateTitleStep = step.do(
  "Generate the project title",
  async () => {
    console.log("Generate the project title");
    const anthropic = createAnthropic({
      apiKey: this.env.ANTHROPIC_API_KEY,
    });

    return {};
  },
);
const generateNotesStep = step.do(
  "Generate the project notes",
  async () => {
    console.log("Generate the project notes");
    return {};
  },
);
// option A
await step.do("Await all project generation steps", async () => {
  await generateTitleStep;
  await generateNotesStep;
});
// option B
await Promise.all([generateTitleStep, generateNotesStep]);

O

oof2win2•12/6/24, 12:25 AM

and can i await the output of one step in another step? i first need to generate data and then i need to save data - don't want to regen data if only the saving failed

const generateNotesStep = step.do(
  "Generate the project notes",
  async () => {
    console.log("Generate the project notes");
    return "These are some notes returned after awaiting";
  },
);

const saveNotesStep = step.do(
  "Save the project notes",
  async () => {
    const notes = await generateNotesStep
    // save the data to the DB here. notes have been generated and won't regenerate if this retries
    return {};
  },
);

const generateNotesStep = step.do(
  "Generate the project notes",
  async () => {
    console.log("Generate the project notes");
    return "These are some notes returned after awaiting";
  },
);

const saveNotesStep = step.do(
  "Save the project notes",
  async () => {
    const notes = await generateNotesStep
    // save the data to the DB here. notes have been generated and won't regenerate if this retries
    return {};
  },
);

const generateNotesStep = step.do(
  "Generate the project notes",
  async () => {
    console.log("Generate the project notes");
    return "These are some notes returned after awaiting";
  },
);

const saveNotesStep = step.do(
  "Save the project notes",
  async () => {
    const notes = await generateNotesStep
    // save the data to the DB here. notes have been generated and won't regenerate if this retries
    return {};
  },
);

const generateNotesStep = step.do(
  "Generate the project notes",
  async () => {
    console.log("Generate the project notes");
    return "These are some notes returned after awaiting";
  },
);

const saveNotesStep = step.do(
  "Save the project notes",
  async () => {
    const notes = await generateNotesStep
    // save the data to the DB here. notes have been generated and won't regenerate if this retries
    return {};
  },
);

O

oof2win2•12/6/24, 12:27 AM

basically i want to start multiple AI processes asynchronously so that they can finish not in order but all are essentially guaranteed to finish

K

kchro3•12/6/24, 12:51 AM

we're seeing an issue where some workflows are getting stuck in the queue. I only have two queued workflows & nothing concurrently executing & i can't terminate them from the dashboard.

any suggestions here or known issues?

FFocux @skip i asked that some days ago, and currently, you can't. they said they will ...

S

skip•12/6/24, 6:43 AM

Ah thanks for the reply. This is a feature that would make workflows hugely useful, imo!

Ooof2win2 would this be valid workflows code? everything is deterministic as all results a...

D

DeChill•12/6/24, 8:11 AM

According to https://developers.cloudflare.com/workflows/build/rules-of-workflows/, awaiting multiple steps with

Promise.all

Promise.all

is fine.

But nested steps seem like they might cause issues with the retry logic? I would suggest just placing the

saveNotesStep

saveNotesStep

after the

Promise.all

Promise.all

and reading the output of the step. In that case if the "save" step fails, the

generateNotesStep

generateNotesStep

will have cached the response. It might only be an issue if the serialized data exceeds the limits.

DDeChill According to https://developers.cloudflare.com/workflows/build/rules-of-workflow...

O

oof2win2•12/6/24, 8:14 AM

the issue is that generatesNotesStep might complete earlier than generateTextStep, so i want to save it to the db as soon as it generates

O

oof2win2•12/6/24, 8:15 AM

or should i just make it two nested steps? or an async function that awaits the first step and then saves it (two await step.do calls)

O

oof2win2•12/6/24, 8:15 AM

the last one kinda makes sense

D

DeChill•12/6/24, 8:21 AM

If you nest the save step inside the generate step, then I don't think it will cache the generate response if the inner save fails. So I think you need to keep them separate. 2 await steps are probably most idiomatic, but the second will only run when the first is finished.

SSeekerdasbatatas Or via the binding

D

DeChill•12/6/24, 3:19 PM

I really hope getting the workflow output by binding will be implemented in the near future! Is there any roadmap or feedback site for workflows?

had the same issue. hope they fix this. I think this is just a bug where the queued state cannot be

Similar Threads