And retrieving it in the next step again?

Aalex (he/him)And retrieving it in the next step again?

S

Seekerdasbatatas•11/29/24, 11:16 AM

when you need it yes

Aalex (he/him)And retrieving it in the next step again?

1

1984 Ford Laser•11/29/24, 11:27 AM

KV is usually in single milliseconds for hot reads, overall that shouldn't be an issue

A

alex (he/him)OP•11/29/24, 11:36 AM

Good idea, haven’t thought about that approach. I’ll see how it will help

11984 Ford Laser KV is usually in single milliseconds for hot reads, overall that shouldn't be an...

A

alex (he/him)OP•11/29/24, 11:38 AM

Yeah I was also thinking about KV instead of R2, I think just making sure to clean-up that KV is important, but otherwise it should be totally fine. It’s a background job, so not too concerned about latency

F

Focux•11/29/24, 1:38 PM

any idea why i get this error when using this retry policy

{ retries: { limit: 12, delay: '2s', backoff: 'constant' } }

{ retries: { limit: 12, delay: '2s', backoff: 'constant' } }

{ retries: { limit: 12, delay: '2s', backoff: 'constant' } }

{ retries: { limit: 12, delay: '2s', backoff: 'constant' } }

✘ [ERROR] Uncaught (in promise) Error: NOT NULL constraint failed: priority_queue.target_timestamp: SQLITE_CONSTRAINT

✘ [ERROR] Uncaught (in promise) Error: NOT NULL constraint failed: priority_queue.target_timestamp: SQLITE_CONSTRAINT

✘ [ERROR] Uncaught (in promise) Error: NOT NULL constraint failed: priority_queue.target_timestamp: SQLITE_CONSTRAINT

✘ [ERROR] Uncaught (in promise) Error: NOT NULL constraint failed: priority_queue.target_timestamp: SQLITE_CONSTRAINT

F

Focux•11/29/24, 1:39 PM

If I remove the retry policy then I don't get any error

F

Focux•11/29/24, 2:22 PM

would it be possible in the future to await a workflow response inside a workflow? like await would sleep your current workflow instance until the sub-workflow finish

FFocux would it be possible in the future to await a workflow response inside a workflo...

S

Seekerdasbatatas•11/29/24, 2:31 PM

it might (or not) happen in the future, but couldn't you make the sub-workflow trigger another workflow at the end? workflow1 -> sub-workflow -> workflow2

F

Focux•11/29/24, 2:36 PM

i mean, yeah, that could work, but it would be good to have some kind of child workflow concept, like temporal.io

F

Focux•11/29/24, 2:37 PM

if the child workflow doesn't succeed then the parent workflow doesn't succeed either

F

Focux•11/29/24, 2:37 PM

and also it is good for propagating cancellation signals when implemented

F

Focux•11/29/24, 2:38 PM

and for code organization

S

Seekerdasbatatas•11/29/24, 2:40 PM

yeah I completely understand, we'll take your feedback into account

M

micooz•11/29/24, 2:46 PM

How can I processa large zip file (get from R2) across steps (get/unzip/put to R2) ? I saw the maximum persisted state per step is only 1MiB.

Mmicooz How can I processa large zip file (get from R2) across steps (get/unzip/put to R...

S

Seekerdasbatatas•11/29/24, 2:53 PM

In this case, I think that you're better off making (get, unzip, put to R2) into a single step, although you lose some granularity as long you guarantee idempotency you'll be okay

C

Carl•11/29/24, 4:07 PM

really loving workflows so far. I hit the execution limit for my use case and had to use a self spawning approach to get around it. Thanks for giving us this primitive. cool stuff

D

dattaproffs•11/30/24, 5:50 PM

Hi, anyone have a good idea how to fan out and keep track of when all of the fanouts is done to send a webhook.
I want to do a couple of steps and when done send a webhook. The 512 limit is a bit small sometimes and i need to fan out, so how do i best keep track of the workflows. Should i have a orchestrator workflow that spawns the fanouts and keep track that way? Any other good ideas. Thanks

D

drew•12/2/24, 4:53 PM

Hey there. Is there a limit to the number of workflow instances that can be queued after exceeding the concurrency limit? Trying to understand what the expected behavior is in that case

C

Carl•12/2/24, 5:16 PM

Hi. I'm facing issues with workflow instances stuck in a queued state indefinitely and i'm unable to terminate it or anything.

K

kingmesal•12/2/24, 8:58 PM

Does a single workflow instantiation inherit the subrequests limit defined in worker limits?
https://developers.cloudflare.com/workers/platform/limits/

Cloudflare Docs

Limits · Cloudflare Workers docs

Cloudflare Workers plan and platform limits.

CCarl Hi. I'm facing issues with workflow instances stuck in a queued state indefinite...

D

ddsgadget•12/2/24, 9:50 PM

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

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

ddsgadget•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

.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

And retrieving it in the next step again?

Similar Threads

Similar Threads

Similar Threads