i don't mean to be rude in any way, but is there any ETA on the ghost executions? i really find work

i don't mean to be rude in any way, but is there any ETA on the ghost executions? i really find workflows to be the best thing for my usecase, but i can't use them if a certain amount of executions just get killed and not even retried

oof2win2OP•12/16/24, 10:00 AM

or if there is anything on my side that i can do to resolve the issue i'd be happy to do so

Ppeachneo Keen to understand what kind of limit is envisioned longer term for "Concurrent ...

Matt Silverlock•12/16/24, 1:43 PM

For Paid: ballpark 1k-5k per Workflow.

Ooof2win2 i don't mean to be rude in any way, but is there any ETA on the ghost executions...

Diogo Ferreira•12/16/24, 1:45 PM

We are aware of such phenomenon and we are actively working on a fix. Since last week, the chance of getting a ghost execution should have reduced significantly. Further, we are currently testing mechanisms for the system to evict ghost instances. More updates will arrive soon.

oof2win2OP•12/16/24, 1:47 PM

Thank you so much!

MMatt Silverlock For Paid: ballpark 1k-5k per Workflow.

peachneo•12/16/24, 11:24 PM

Thanks good to know - Out of interest, when I look at the DO API, I don't immediately see why it would not be unlimited eventually? Curious what the constraints are

Ppeachneo Thanks good to know - Out of interest, when I look at the DO API, I don't immedi...

Matt Silverlock•12/17/24, 12:15 AM

We’re still assessing limits. Workflows isn’t just a single DO - we’re doing all of the orchestration, metrics, etc.

Tushar•12/17/24, 2:45 PM

can i write workflows in rust

TTushar can i write workflows in rust

Matt Silverlock•12/17/24, 4:47 PM

Not yet. Something we want to land closer to the GA. Focusing on the foundations first.

Tushar•12/17/24, 5:01 PM

gotcha, good luck ^^

DeChill•12/17/24, 7:07 PM

Are there any updates on getting the Workflow return value through the binding, or Is that on the roadmap?
Adding the Cloudflare API SDK just to get the workflow return value seems to be a bit too much.

I currently have to do a workaround by adding an additional unnecessary step to the end of my workflows, just so I can access the value from the

InstanceStatus

InstanceStatus

output

output

property, which only contains an array with the individual step outputs.

DDeChill Are there any updates on getting the Workflow return value through the binding, ...

Matt Silverlock•12/17/24, 7:47 PM

What do you consider the "return" value here? Steps return values. The

run

run

method does not, so there's not a "singular" value.

MMatt Silverlock What do you consider the "return" value here? Steps return values. The `run` met...

DeChill•12/17/24, 7:55 PM

Thanks for the reply Matt. The workflow run method definition has an return value that you can type (it isn't defined as Promise<void>) and the Workflow output (what the

run

run

method returns) is also prominently shown on the Workflow dashboard. So I would assume this is an intended feature of workflows.

DeChill•12/17/24, 7:59 PM

In the Cloudflare API "Get Logs And Status From Instance" endpoint, the workflow output is also returned separately from the "steps" results. But confusingly, the

output

output

property of the Binding

InstanceStatus

InstanceStatus

contains the step results, not the workflow output.

DDeChill Thanks for the reply Matt. The workflow run method definition has an return valu...

Matt Silverlock•12/17/24, 8:19 PM

Not quite - something we're iterating on, specifically because returning a single (size limited) string can be confusing here.

MMatt Silverlock Not quite - something we're iterating on, specifically because returning a singl...

DeChill•12/17/24, 8:20 PM

hmm okay, from my testing the type of the API docs are wrong. It does indeed return an object value

DDeChill In the Cloudflare API "Get Logs And Status From Instance" endpoint, the workflow...

Seekerdasbatatas•12/17/24, 8:20 PM

But confusingly, the output property of the Binding InstanceStatus contains the step results, not the workflow output.

You mean in local dev, right? what's the behaviour on a real workflow?

SSeekerdasbatatas > But confusingly, the output property of the Binding InstanceStatus contains th...

DeChill•12/17/24, 8:23 PM

hmm it seems like you are right! I just tested it again with my deployed workflow and I do indeed get the workflow output there.

DDeChill hmm okay, from my testing the type of the API docs are wrong. It does indeed ret...

Seekerdasbatatas•12/17/24, 8:23 PM

sorry about that

it should be an unknown there - i'll look into it but I think it's an openapi 3.0 limitation

DeChill•12/17/24, 8:24 PM

That is good to know! I hope miniflare will be updated soon to support the same behavior

DDeChill That is good to know! I hope miniflare will be updated soon to support the same ...

Seekerdasbatatas•12/17/24, 8:24 PM

yhep i'm looking into it right now

DDeChill That is good to know! I hope miniflare will be updated soon to support the same ...

Seekerdasbatatas•12/17/24, 8:57 PM

https://github.com/cloudflare/workers-sdk/pull/7575 there you go

GitHub

Make workflow `instance.status()` return output equal to production...

Previously, in local dev, the output field would return the list of successful steps outputs in the workflow. This is not expected behavior compared to production workflows (where the output is the...

SSeekerdasbatatas https://github.com/cloudflare/workers-sdk/pull/7575 there you go

DeChill•12/17/24, 9:17 PM

that was quick

looking forward to it! Good idea to keep the step outputs available for debugging locally

SSeekerdasbatatas I'll check it out next week 🧑‍🍳

alex (he/him)•12/18/24, 6:19 AM

Any updates or issues I can subscribe/follow to, to track progress on this?

Avi•12/19/24, 3:49 AM

seems like there might be some sort of outage? when i create new workflows, they have no steps, and when I try to pause or terminate the instances in the dashboard, those API calls return 500 errors like:

{
  "success": false,
  "messages": [],
  "errors": [
    {
      "code": 10001,
      "message": "workflows.api.error.internal_server"
    }
  ],
  "result": null
}

{
  "success": false,
  "messages": [],
  "errors": [
    {
      "code": 10001,
      "message": "workflows.api.error.internal_server"
    }
  ],
  "result": null
}

Avi•12/19/24, 3:50 AM

they also all have a start time of "pending"

Avi•12/19/24, 3:50 AM

oh wait - i think i'm running up against the 100 concurrency limit

Avi•12/19/24, 3:52 AM

i would have assumed that workflows that aren't actually running (and are just sleeping) would not count towards the 100 concurrency limit...?

DDiogo Ferreira The 100 instance limit refer to instances running. Regarding instances in a slee...

Avi•12/19/24, 3:58 AM

how long is "eventually"? I'm seeing many instances, whose first step is a simple

await step.sleep('wait 24 hours', '24 hours')

await step.sleep('wait 24 hours', '24 hours')

, which have been stuck in the "running" phase for many hours (30+)

Avi•12/19/24, 3:59 AM

this is apparently deadlocking my whole account, since these instances which should be

Waiting

Waiting

are actually

Running

Running

, and counting towards the 100 concurrency limit

AAvi seems like there might be some sort of outage? when i create new workflows, they...

Seekerdasbatatas•12/19/24, 7:12 PM

if you can send me your account id, workflow name and instance id I can look it up

Aalex (he/him)Any updates or issues I can subscribe/follow to, to track progress on this?

Seekerdasbatatas•12/19/24, 7:17 PM

update your

@cloudflare/worker-types

@cloudflare/worker-types

and should be on

WorkflowEvent.instanceId

WorkflowEvent.instanceId

Seekerdasbatatas•12/19/24, 7:18 PM

FYI y'all, we've bumped step limits again to 1024

SSeekerdasbatatas if you can send me your account id, workflow name and instance id I can look it ...

Avi•12/19/24, 7:39 PM

https://dash.cloudflare.com/12b33d4134fdbae99a1ab3bbf272e8ea/workers/workflows/gg-production-miniavocado-scheduler/instance/0980a72b-e12e-46d4-81f3-726bcd82bec9

Avi•12/19/24, 7:40 PM

thanks for your help! if you look at this one, the instance has been stuck in the "running" status for >24 hours

Avi•12/19/24, 7:40 PM

when it should actually be Waiting state

Avi•12/19/24, 7:41 PM

this is a serious issue for us because it's causing us to hit the 100 concurrency limit

Avi•12/19/24, 7:41 PM

we're actually rebuilding our own task system outside of workflows because it's so broken

AAvi this is a serious issue for us because it's causing us to hit the 100 concurrenc...

Seekerdasbatatas•12/19/24, 8:02 PM

You can try to terminate those hanging ones, to free up space - feel free to send any instance thats stuck to my dms (to not clog up this chat)

SSeekerdasbatatas FYI y'all, we've bumped step limits again to 1024 🚀 🧑‍🍳

can•12/19/24, 8:33 PM

i love y'all

@Seekerdasbatatas thanks for keeping updates coming our way and improving the product each day according to the user needs. you guys are the best!

Wilson Wong•12/20/24, 3:15 AM

Howdy all, I'm trying about workflow and saw this doc to running it locally, https://developers.cloudflare.com/workflows/build/local-development/, is there a way for me to test out the workflow? I know that

npx wrangler workflow

npx wrangler workflow

targets production api. Do I need to setup a local worker to call my local workflow?

Cloudflare Docs

Local Development · Cloudflare Workflows docs

Workflows support local development using Wrangler, the command-line interface for Workers. Wrangler runs an emulated version of Workflows compared to the one that Cloudflare runs globally.

WWilson Wong Howdy all, I'm trying about workflow and saw this doc to running it locally, htt...

Matt Silverlock•12/20/24, 1:17 PM

The doc you linked shows the steps: https://developers.cloudflare.com/workflows/build/local-development/#start-a-local-development-session

Cloudflare Docs

Local Development · Cloudflare Workflows docs

Workflows support local development using Wrangler, the command-line interface for Workers. Wrangler runs an emulated version of Workflows compared to the one that Cloudflare runs globally.

Fernando Barroso•12/20/24, 9:25 PM

Is there a way to delete workflows on our accounts? I can’t seem to find it either in the dashboard or api

Fernando Barroso•12/20/24, 10:28 PM

Oops! What happens if you delete the worker bound to a workflow? Can that workflow still be used by another worker?

hkdobrev•12/21/24, 6:45 AM

I'm using workflows and I really like the built-in design to retry individual steps, very much like a multi-queue solution for each step.

However, I'm also using queues to trigger N instances of the workflow as I want to space out some external calls, so I'm using delay with the queue.
But I'd very much like the workflow to receive the original batch.
This would allow for a much more robust acknowledgement and retry mechanism. If the workflow has access to the JS API of the queue batch, it will be able to control acknowledgment of the message. By retrying the queue message, it will be able to revert back executed steps by retrying the queue message and triggering a new workfow instance resetting the state.
The step sleep is not enough for that.

Currently, I need to resort to acknowledging all messages in the queue batch as soon as the workflow is triggered regarless if it's successful.

SSeekerdasbatatas update your `@cloudflare/worker-types` and should be on `WorkflowEvent.instanceI...

alex (he/him)•12/21/24, 7:06 AM

Doesn't seem to work with

wrangler types --experimental-include-runtime

wrangler types --experimental-include-runtime

D Trombett•12/21/24, 11:08 AM

Assuming that I have a workflow which at the end returns something, can I later retrieve that value using

env.WORKFLOW.get(id).status().output

env.WORKFLOW.get(id).status().output

(something like a sort of kv?) or is it something one shouldn't rely on (e.g. expires after some time)?

D Trombett•12/21/24, 11:35 AM

Ah, I guess this is part of the following limit:

Retention limit for completed Workflow state: 3 days; 30 days

Ashley•12/21/24, 6:11 PM

Just as an FYI, I think there's some out of date info in the docs referring to

event.params

event.params

(e.g. https://developers.cloudflare.com/workflows/get-started/guide/) whereas I now think it's

event.payload

event.payload

(changing this fixed it for me so guessing event.params was old?)

Warren•12/22/24, 4:35 AM

Asking a question re the

Serialized RPC arguments or return values are limited to 1MiB

Serialized RPC arguments or return values are limited to 1MiB

error

the limits:

maximum persisted state per step is 1MiB
Workers return value can only be 1MiB

as such, what I'm trying to do is to ensure that the work done in step in is smaller than the 1MiB limit before returning it.

I am using this to get the size of the return value

export function getApproximateSizeInBytes(obj: unknown) {
  return new TextEncoder().encode(JSON.stringify(obj)).length;
}

export function getApproximateSizeInBytes(obj: unknown) {
  return new TextEncoder().encode(JSON.stringify(obj)).length;
}

however, I notice that the value returned and the actual value shown when an error is thrown can be quite different.

how can I reliably check what is the size of a return value before returning it?

(guess this is not specific to Workflows, but it's relevant in this context because a workaround I've seen is to use ReadableStream, but that wouldn't work because of the max persisted state per step limit)

i don't mean to be rude in any way, but is there any ETA on the ghost executions? i really find work

Similar Threads

Similar Threads

Similar Threads