Yeah, I don't know. i don't feel comfortable sharing Account IDs here. Anyway, the bug is that if a

D

ddsgadgetOP•11/25/24, 5:31 PM

BTW, Workflows are simply amazing. This is the greatest thing, in my opinion, to happen to Workers since I started using them a few years ago. I didn't realize it was beta, and I already moved alot of functionality to Workflows and I am just hoping not much changes when it is out of beta.

Dddsgadget Yeah, I don't know. i don't feel comfortable sharing Account IDs here. Anyway, t...

M

Matt Silverlock•11/25/24, 5:44 PM

Account IDs are safe to share. You can't do anything with them.

d458dbe698b8eef41837f941d73bc5b3

d458dbe698b8eef41837f941d73bc5b3

d458dbe698b8eef41837f941d73bc5b3

d458dbe698b8eef41837f941d73bc5b3 is mine.

Dddsgadget Yeah, I don't know. i don't feel comfortable sharing Account IDs here. Anyway, t...

M

Matt Silverlock•11/25/24, 5:45 PM

Without an account ID we can't easily track it down: IDs are scoped to an account.

森

森@VerseLink (RW)•11/25/24, 8:45 PM

Uncaught SyntaxError: The requested module 'cloudflare:workers' does not provide an export named 'WorkflowStep'

uhm, did I break something...?

MMatt Silverlock I'm suggesting doing neither: typing the `params` property doesn't propagate typ...

F

Focux•11/25/24, 9:44 PM

I'd love to use generics when defining the workflow binding so I get the autocomplete when calling

create

create

. This would also match other Cloudflare bindings like DurableObjects, which also uses generics.

A

alex (he/him)•11/26/24, 5:49 AM

Concurrent Workflow instances (executions)

Concurrent Workflow instances (executions)

Concurrent Workflow instances (executions)

Concurrent Workflow instances (executions) is that per Workflow or per Worker Script? So if I define multiple workflows in the same worker script, do all of them have the concurrency. Would Workflow B be blocked by a lot of Workflow A instances?

A

alex (he/him)•11/26/24, 5:57 AM

And does anyone has thoughts about these two options. Is there any difference between them, and if so what is the difference?

Original message was deleted

森

森@VerseLink (RW)•11/26/24, 6:12 AM

i was on wrangler 3.90.0 (i did try to update it, and delete the .wrangler file)

森

森@VerseLink (RW)•11/26/24, 6:12 AM

i copied the type definition as a hack for now

Aalex (he/him)`Concurrent Workflow instances (executions)` is that per Workflow or per Worker ...

M

Matt Silverlock•11/26/24, 11:44 AM

It’s account wide (all of your Workflows). We’ll be bringing per-Workflow controls, and the limit on the paid plan will increase as we go.

MMatt Silverlock It’s account wide (all of your Workflows). We’ll be bringing per-Workflow contro...

A

apolodoro•11/26/24, 6:58 PM

Hey Matt, Is sleeping until event (webhook) planned for this year?

S

Seekerdasbatatas•11/27/24, 6:33 PM

We've bumped up step limits to 512 per workflow: https://developers.cloudflare.com/workflows/reference/limits/

happy thanksgiving to y'all

Cloudflare Docs

Limits | Cloudflare Workflows docs

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

K

kchro3•11/28/24, 1:57 AM

I've seen several comments about this error response:

✘ [ERROR] An RPC stub was not disposed properly. You must call dispose() on all stubs in order to let the other side know that you are no longer using them. You cannot rely on the garbage collector for this because it may take arbitrarily long before actually collecting unreachable objects. As a shortcut, calling dispose() on the result of an RPC call disposes all stubs within it.

✘ [ERROR] An RPC stub was not disposed properly. You must call dispose() on all stubs in order to let the other side know that you are no longer using them. You cannot rely on the garbage collector for this because it may take arbitrarily long before actually collecting unreachable objects. As a shortcut, calling dispose() on the result of an RPC call disposes all stubs within it.

✘ [ERROR] An RPC stub was not disposed properly. You must call dispose() on all stubs in order to let the other side know that you are no longer using them. You cannot rely on the garbage collector for this because it may take arbitrarily long before actually collecting unreachable objects. As a shortcut, calling dispose() on the result of an RPC call disposes all stubs within it.

✘ [ERROR] An RPC stub was not disposed properly. You must call dispose() on all stubs in order to let the other side know that you are no longer using them. You cannot rely on the garbage collector for this because it may take arbitrarily long before actually collecting unreachable objects. As a shortcut, calling dispose() on the result of an RPC call disposes all stubs within it.

but i don't think anyone's responded to them. Any idea what this is about?

Kkchro3 I've seen several comments about this error response: ``` ✘ [ERROR] An RPC stub...

1

1984 Ford Laser•11/28/24, 3:04 AM

I think if you need a stub after it has returned its value, you should

dup()

dup()

dup()

dup() it then

dispose()

dispose()

dispose()

dispose() of the original?

11984 Ford Laser I think if you need a stub after it has returned its value, you should `dup()` i...

K

kchro3•11/28/24, 3:14 AM

got it, thanks

A

anirudh•11/28/24, 4:57 AM

I want to create a workflow which takes an input of list of APIs to be called. I want to loop over the list and call the API in a step.do, do workflows support this?

A

alex (he/him)•11/28/24, 10:17 AM

If I rename a workflow binding, it get's added as a new entry to the dashboard.. Is there a way to delete registered workflows? How can I get rid of them in the UI and remove them from the system completely.. otherwise we end up with a lot of stale stuff

S

Seekerdasbatatas•11/28/24, 11:03 AM

we don't a delete endpoint for workflows - it's coming :soonsoontm:

1

1984 Ford Laser•11/28/24, 11:04 AM

I cant read

A

alex (he/him)•11/28/24, 1:57 PM

I'm getting this:

UNDEFINED_VALUE: Undefined values are not allowed

UNDEFINED_VALUE: Undefined values are not allowed

UNDEFINED_VALUE: Undefined values are not allowed

UNDEFINED_VALUE: Undefined values are not allowed
My Params type look like this:

type Params = {
    machine_id: number;
    target_language_id: number;
    techdata_template_id?: number;
    servicedata_template_id?: string;
};

type Params = {
    machine_id: number;
    target_language_id: number;
    techdata_template_id?: number;
    servicedata_template_id?: string;
};

type Params = {
    machine_id: number;
    target_language_id: number;
    techdata_template_id?: number;
    servicedata_template_id?: string;
};

type Params = {
    machine_id: number;
    target_language_id: number;
    techdata_template_id?: number;
    servicedata_template_id?: string;
};

It looks like Workflows does not support optional params, is that correct?

SSeekerdasbatatas we don't a delete endpoint for workflows - it's coming :soonsoontm:

A

alex (he/him)•11/28/24, 3:12 PM

Sounds good. I have like roughly 10k instances brokenly queued. How to bulk terminate them?

F

Focux•11/28/24, 3:19 PM

is there a way to know within a step if it's retrying, and if so, can you get the error that made it fail?

A

alex (he/him)•11/28/24, 7:41 PM

Did we just loose the Wall Time per Step in the Dashboard? It was very nice to see how long a step took for a specific instance

A

alex (he/him)•11/28/24, 8:16 PM

What are some ideas around reducing state byte size. I'm currently facing an issue where I either reach the step count limit or subrequest limit, so the solution is to combine things, but then I'm facing the size limit. I think the state size limit should be easier to increase maybe to 10MiB?

Serialized RPC arguments or return values are limited to 1MiB, but the size of this value was: 2221149 bytes.

Serialized RPC arguments or return values are limited to 1MiB, but the size of this value was: 2221149 bytes.

Serialized RPC arguments or return values are limited to 1MiB, but the size of this value was: 2221149 bytes.

Serialized RPC arguments or return values are limited to 1MiB, but the size of this value was: 2221149 bytes.

Aalex (he/him)What are some ideas around reducing state byte size. I'm currently facing an iss...

S

Seekerdasbatatas•11/29/24, 10:57 AM

In these cases I would recommend storing the result to KV/R2 and just return the key

SSeekerdasbatatas In these cases I would recommend storing the result to KV/R2 and just return the...

A

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

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

ddsgadgetOP•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.

Yeah, I don't know. i don't feel comfortable sharing Account IDs here. Anyway, the bug is that if a

Similar Threads

Similar Threads

Similar Threads