Hey so i have a rag workflow pipeline for a hackathon the issue is the steps are failing with "Too

Hey so i have a rag workflow pipeline for a hackathon the issue is the steps are failing with
"Too many subrequests." for generating embeddings and storing it into neon db(its a requirement thats why i cant use service binding to D1). are there any subrequest limits in workflows ??

-free tier account

yzziKOP•12/15/24, 4:34 PM

Ok found it 50 subrequests only

YyzziK Hey so i have a rag workflow pipeline for a hackathon the issue is the steps are...

Matt Silverlock•12/15/24, 5:03 PM

Same as Workers: 50 on free, 1000 on Paid.

YyzziK Hey so i have a rag workflow pipeline for a hackathon the issue is the steps are...

Matt Silverlock•12/15/24, 5:04 PM

https://developers.cloudflare.com/workflows/reference/limits/

Cloudflare Docs

Limits · Cloudflare Workflows docs

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

yzziKOP•12/15/24, 5:04 PM

Thats so bad

yzziKOP•12/15/24, 5:04 PM

I think I'll have to invoke other workflows from the current one to bypass it

yzziKOP•12/15/24, 5:04 PM

I hope ?

YyzziK I think I'll have to invoke other workflows from the current one to bypass it

Matt Silverlock•12/15/24, 5:05 PM

You still have a daily limit on total invocations (it's a free plan). 50 subrequests per Workflow instance is still a fair few.

yzziKOP•12/15/24, 5:07 PM

It's 100 invocations per day right. I need to process 50~200 documents at max so maybe send them in a batch of 25-40 to other workflows

YyzziK It's 100 invocations per day right. I need to process 50~200 documents at max so...

Matt Silverlock•12/15/24, 5:08 PM

It’s 100,000 per day (see the docs I linked)

yzziKOP•12/15/24, 5:09 PM

Nice

yzziKOP•12/15/24, 9:29 PM

Can I call the worker's endpoint from the workflow in the same application? How do I use service binding in the same worker.

Does using a service binding like this, I can avoid reaching 50 subrequests limit ?

peachneo•12/16/24, 3:21 AM

Keen to understand what kind of limit is envisioned longer term for "Concurrent Workflow instances" if anyone from CF can speak to that?

oof2win2•12/16/24, 9:58 AM

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

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

oof2win2•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 InstanceStatusInstanceStatus outputoutput 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 runrun 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 runrun 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 outputoutput property of the Binding InstanceStatusInstanceStatus 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 WaitingWaiting are actually RunningRunning, 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.instanceIdWorkflowEvent.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

Hey so i have a rag workflow pipeline for a hackathon the issue is the steps are failing with "Too

Similar Threads