Yeah as you were typing I had a similar thought, as then you'd need to handle retries for the "failu

Yeah as you were typing I had a similar thought, as then you'd need to handle retries for the "failure step handlers" and it might get a bit confusing - perhaps just in the docs it might be good to have your example to document it for steps, and then yeah for overall workflows it'd be lovely to have a failure handler

I guess for now... could you literally wrap the entire

run

run

function in try/catch and that would effectively act as a "on failure" handler? As it'd catch any step failure after retries based on what you said

AAshley Yeah as you were typing I had a similar thought, as then you'd need to handle re...

Seekerdasbatatas•1/6/25, 11:22 AM

I guess for now... could you literally wrap the entire run function in try/catch and that would effectively act as a "on failure" handler?

yhep, that would work

AshleyOP•1/6/25, 11:27 AM

Awesome, thank you - really enjoying workflows so far overall

AAshley Awesome, thank you - really enjoying workflows so far overall 🤓

Seekerdasbatatas•1/6/25, 11:50 AM

@Jacob | CI has some nice abstractions for o11y: https://github.com/jahands/workers-monorepo-public/tree/main/packages/workflows-helpers/src

GitHub

workers-monorepo-public/packages/workflows-helpers/src at main · ja...

A sample of my monorepo used to deploy Cloudflare Workers - jahands/workers-monorepo-public

Akash Gupta•1/6/25, 12:01 PM

Hi Cloudflare Team,
I'm currently using QUIC.cloud nameservers for my domain and I'd like to start offloading my media content to an R2 bucket. However, I want to avoid changing my existing nameserver and DNS settings if possible.
Currently, I'm using a subdomain (r2.dev) for my R2 bucket. Is there a way to configure Cloudflare to serve media from my R2 bucket while keeping my QUIC.cloud nameservers and current DNS records intact?

AAkash Gupta Hi Cloudflare Team, I'm currently using QUIC.cloud nameservers for my domain and...

Hello, I’m Allie!•1/6/25, 12:57 PM

I believe Custom Domains Setup should walk you through how it works

Luca (steebchen)•1/6/25, 1:13 PM

Is it possible to use workflows with cf pages (nextjs specifically)?

Original message was deleted

Luca (steebchen)•1/6/25, 2:28 PM

would be super cool to have that available in pages so I don't have to depend on an external workflows service. but fair, it is still beta after all, just a suggestion

Original message was deleted

Luca (steebchen)•1/6/25, 2:40 PM

understood, thanks. I might look into Workers Assets but not a priority right now

flash716•1/6/25, 9:12 PM

If I have a long delay between step failure retries (say 60 minutes or even longer) will the workflow cycle out of active state in regard to the Concurrent Workflow Instances limit while it's waiting to retry (similar to sleep) or will it stay active the entire time it's waiting to retry?

Ddarren Hello! I’ve been building with Workflows for the past couple of weeks. The ergon...

darren•1/7/25, 2:07 PM

Is it possible that these network requests could be failing because the workflow is executing in a restricted region? I've heard of OpenAI blocking some regions, but I'd be surprised if Cloudflare's own AI product would also block.

I'm having a tough time figuring out another reason why these requests would fail so often. Maybe worth noting, but getget requests are ok for the most part, the requests that are failing are postpost.

Here's an example of the type of request I'm talking about.

      const generatedContent = await step.do("Write content", async () => {
        const ai = new OpenAI({
          apiKey: this.env.CLOUDFLARE_AI_TOKEN,
          baseURL: `https://api.cloudflare.com/client/v4/accounts/{my account id}/ai/v1`,
        });

        const result = await ai.chat.completions.create({
          model: "@cf/meta/llama-3.1-8b-instruct",
          messages: [...example]
        })

        return result.choices[0].message.content;
      })

      const generatedContent = await step.do("Write content", async () => {
        const ai = new OpenAI({
          apiKey: this.env.CLOUDFLARE_AI_TOKEN,
          baseURL: `https://api.cloudflare.com/client/v4/accounts/{my account id}/ai/v1`,
        });

        const result = await ai.chat.completions.create({
          model: "@cf/meta/llama-3.1-8b-instruct",
          messages: [...example]
        })

        return result.choices[0].message.content;
      })

oof2win2•1/7/25, 2:42 PM

heya, is there any estimate on increasing the concurrency of workflows?

Ooof2win2 heya, is there any estimate on increasing the concurrency of workflows?

Isaac McFadyen•1/7/25, 2:48 PM

https://canary.discord.com/channels/595317990191398933/1296923707792560189/1318211982578548757 and https://canary.discord.com/channels/595317990191398933/1296923707792560189/1322620898062372865

Isaac McFadyen•1/7/25, 2:48 PM

TLDR: not really, it's planned but no ETA

oof2win2•1/7/25, 2:48 PM

make sense ty

BBahaa Any word on this? Even tried wrapping my step with a try/catch with retries set ...

Seekerdasbatatas•1/7/25, 8:05 PM

Is the error happening with new instances?

Seekerdasbatatas•1/7/25, 8:11 PM

Ah I see, can you give me your account id? I'll escalate this up

Seekerdasbatatas•1/7/25, 8:12 PM

If you prefer yes, but account ids are safe to share publicly

Lucas G•1/8/25, 2:09 AM

A workflow that was working fine is now erroring out with only this:
TypeError: The RPC receiver does not implement the method "run".

What could cause this given that it was working hours ago?

LLucas G A workflow that was working fine is now erroring out with only this: TypeError: ...

Diogo Ferreira•1/8/25, 11:25 AM

Sorry to hear that Lucas. Can you please share your account id for our team to take a look into it?

DDiogo Ferreira Sorry to hear that Lucas. Can you please share your account id for our team to t...

Lucas G•1/8/25, 2:04 PM

facce5f30267ea8a9773949bfae2feff

LLucas G facce5f30267ea8a9773949bfae2feff

Diogo Ferreira•1/8/25, 2:21 PM

Thank you

Lucas G•1/8/25, 3:20 PM

Sorted now, thanks to Diogo.

LLucas G A workflow that was working fine is now erroring out with only this: TypeError: ...

Diogo Ferreira•1/8/25, 3:21 PM

Just to recap, and for reference if anyone face an identical issue, this was caused because the wrangler.toml file didn't contain the necessary

[[workflows]]

[[workflows]]

definition

ajgeiss0702•1/8/25, 6:51 PM

it looks like the average wall time displayed in the dashboard is waaaay off

ajgeiss0702•1/8/25, 6:53 PM

not end-of-the-world stuff, but a bit odd

ajgeiss0702•1/8/25, 6:54 PM

and it displays a different, also wrong, number in the Metrics tab

ajgeiss0702•1/8/25, 6:54 PM

Ddarren Is it possible that these network requests could be failing because the workflow...

darren•1/8/25, 10:41 PM

Sorry about bumping this one again, but I’m stumped.

Is there a way to see if I’m somehow bumping up against limits? The actual processing time shouldn’t be significant here. The network requests may be a bit slow, but from what I can gather from the docs, waiting on IO shouldn’t affect the limits.

Any insights or debugging advice would be appreciated.

DDiogo Ferreira Just to recap, and for reference if anyone face an identical issue, this was cau...

Lucas G•1/8/25, 10:46 PM

Unfortunately, that was not the cause. Same issue is happening again even though no changes have been made.

Ddarren 👋 Sorry about bumping this one again, but I’m stumped. Is there a way to see i...

Matt Silverlock•1/9/25, 8:48 AM

Can you share more details? What does the full error message return? Just connection error? How many concurrent Workflows are running?

flash716•1/10/25, 4:32 PM

Anybody have any insight on this question?

workflows

Seekerdasbatatas•1/10/25, 6:42 PM

hey everyone, I've done on my free time a batteries-included library for Workflows called Flowcesinha: https://github.com/LuisDuarte1/flowcesinha

Custom storage engines and lazy step results (R2 included) so that, you can store more state inside of an step (and you can bring your own storage engine!);
Error reporting (Sentry provided in flowcesinha-sentry) and Workflow failure handler;
Reversable steps: ability to add a revert callback in case that the workflow fails;
Durable fetch: ability to fetch from APIs with dynamic retries (that come from the Retry-After header);
Functional primitives: doMap (map but every call is done inside of a step);
... more to come soon!

what would you guys want to see next?

GitHub

GitHub - LuisDuarte1/flowcesinha: A utility libraries for Cloudflar...

A utility libraries for Cloudflare Workflows. Contribute to LuisDuarte1/flowcesinha development by creating an account on GitHub.

SSeekerdasbatatas hey everyone, I've done on my free time a **batteries-included** library for Wor...

Focux•1/11/25, 1:38 PM

wooah! that's literally my wishlist for workflows, thank you for your work!

Focux•1/11/25, 1:49 PM

I know you did that in your free time, and I really appreciate it, i'll be using it, but can we expect these features to be built-in in the future?

Idle•1/11/25, 11:13 PM

https://developers.cloudflare.com/workers/configuration/cron-triggers/

Cloudflare Docs

Cron Triggers · Cloudflare Workers docs

Enable your Worker to be executed on a schedule.

Idle•1/11/25, 11:13 PM

bubblewrap•1/12/25, 11:06 AM

hi team, I am struggling with creating/accessing database and service bindings for a workflow. Even though the bindings are defined in the wrangler.toml, the only binding that is accessible during the deployment is the workflow binding, DB and AGENT_LOOP are undefined.

wrangler.toml:
[[workflows]]
name = "wf-ainf-run-snap"
binding = "RUN_SNAP_WORKFLOW"
class_name = "RunSnapWorkflow"
main = "src/index.ts"
compatibility_date = "2024-01-01"
compatibility_flags = ["nodejs_compat"]

[[d1_databases]]
binding = "DB"
database_name = "ainfiltrators"
database_id = "xxxxx"

[[services]]
binding = "AGENT_LOOP"
service = "agent-loop"

deploy output:
Your worker has access to the following bindings:

Workflows:
- RUN_SNAP_WORKFLOW: RunSnapWorkflow

What am i missing here?
thanks in advance!

Yeah as you were typing I had a similar thought, as then you'd need to handle retries for the "failu

Similar Threads