instance is: 079dd27c-cb60-45c9-a0f1-8bad4b169c97

Dddsgadget instance is: 079dd27c-cb60-45c9-a0f1-8bad4b169c97

M

Matt Silverlock•11/25/24, 2:13 PM

Need both.

D

ddsgadgetOP•11/25/24, 2:24 PM

you can probably find my account id, i don't want to add it here

Dddsgadget you can probably find my account id, i don't want to add it here

H

Hello, I’m Allie!•11/25/24, 3:04 PM

Account IDs are safe to share, as without credentials, they cannot be used for anything

DDaniel Jakobsen I think a better type api would be to use the generic type parameters, something...

M

Matt Silverlock•11/25/24, 3:20 PM

Thanks for the PR, although I don't get the benefit here - if you're passing your type as params, the type information doesn't carry through to the Workflow itself (it can't by definition: types don't work like that in JS).

Typing the

params

params

property in the

create

create

call doesn't propagate through to

WorkflowEvent

WorkflowEvent

because there is a serialization step in the middle.

What are you actually trying to achieve here?

M

Matt Silverlock•11/25/24, 3:22 PM

as

as

isn't a validation either: it casts to that type. If you need to validate the params, use something like

zod

zod

DDaniel Jakobsen Code organization, I have this structure ``` src/index.ts src/route/some_route.t...

M

Matt Silverlock•11/25/24, 3:28 PM

I'm suggesting doing neither: typing the

params

params

property doesn't propagate type information anywhere, because the

create

create

call doesn't return anything about your params.

DDaniel Jakobsen Workflows is really powerful! reduces a bunch of headache 🫠 Is it expected to s...

M

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

Yes, we don't take things away from the free tier. It'll just have the limits we advertise: great for prototyping/hobby projects, but if you want to ship something production scale, you'll likely need to upgrade to paid.

HHello, I’m Allie!Account IDs are safe to share, as without credentials, they cannot be used for a...

D

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

Yeah, I don't know. i don't feel comfortable sharing Account IDs here. Anyway, the bug is that if a workflow is in a queued status it is impossible to get it out of that status. can't terminate it, pause it or do anything.

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

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)

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

it then

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

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.

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

instance is: 079dd27c-cb60-45c9-a0f1-8bad4b169c97

Similar Threads

Similar Threads

Similar Threads