Just to recap, and for reference if anyone face an identical issue, this was caused because the wran

A

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

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

A

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

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

A

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

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

A

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

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

D

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

L

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

M

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?

F

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

Anybody have any insight on this question?

workflows

S

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

F

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

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

F

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?

I

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.

I

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

B

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!

Bbubblewrap hi team, I am struggling with creating/accessing database and service bindings f...

H

Hello, I’m Allie!•1/12/25, 11:30 AM

This looks like an issue with TOML inheritance. Try this

wrangler.json

wrangler.json

instead:

wrangler.json516B

H

Hello, I’m Allie!•1/12/25, 11:31 AM

Also note that for Service Bindings to work, you need to have a separate

wrangler dev

wrangler dev

wrangler dev

wrangler dev running with the

agent-loop

agent-loop

agent-loop

agent-loop Worker

B

bubblewrap•1/12/25, 2:59 PM

Thanks! Now I am struggling with calling one workflow from another. Is this possible? Both workflows are folders in the same monorepo. Let's say I want to call RunSnapWorkflow from RunEpisodeWorkflow. The things I have trouble with:

When I add the workflow_b binding to workflow_a wrangler.toml, i get a deploy error: "Your Worker depends on the following Workflows, which are not exported in your entrypoint file: RunSnapWorkflow. You should export these objects from your entrypoint, src/index.ts."
If i copy the RunSnapWorkflow class definition to RunEpisodeWorkflow, i can deploy. but when i call RunSnapWorkflow.create() "I get an error: Error: workflow.not_found "

I read through all the docs but i cannot find an example where one workflow calls another

Should i bind RunSnapWorkflow as a service and use fetch interface?

Bbubblewrap Thanks! Now I am struggling with calling one workflow from another. Is this poss...

B

bubblewrap•1/12/25, 4:12 PM

when i try to bind as a service and call via fetch, i get "workflow.not_found" error... Completely stumped here

Bbubblewrap Thanks! Now I am struggling with calling one workflow from another. Is this poss...

M

Matt Silverlock•1/12/25, 4:30 PM

https://developers.cloudflare.com/workflows/build/workers-api/#cross-script-calls

Cloudflare Docs

Workers API · Cloudflare Workflows docs

This guide details the Workflows API within Cloudflare Workers, including methods, types, and usage examples.

Bbubblewrap Thanks! Now I am struggling with calling one workflow from another. Is this poss...

M

Matt Silverlock•1/12/25, 4:31 PM

Without your

wrangler.json

wrangler.json

files it is hard to guess at what you are doing though. There’s nothing special here: make sure you are exporting each Workflow, and have a binding to the ones you want to call via the Workers API.

L

Luca (steebchen)•1/12/25, 10:35 PM

can I list locally run workflows?

pnpm wrangler workflows list

pnpm wrangler workflows list

pnpm wrangler workflows list

pnpm wrangler workflows list doens't return anything as I am just testing in dev for now and want to run the local workflow runs

L

Luca (steebchen)•1/12/25, 10:38 PM

also, is there something equivalent as Inngest's NonRetriableError? https://www.inngest.com/docs/features/inngest-functions/error-retries/inngest-errors#prevent-any-additional-retries

LLuca (steebchen)also, is there something equivalent as Inngest's NonRetriableError? https://www....

M

Matt Silverlock•1/13/25, 1:26 PM

https://developers.cloudflare.com/workflows/build/workers-api/#nonretryableerror

Cloudflare Docs

Workers API · Cloudflare Workflows docs

This guide details the Workflows API within Cloudflare Workers, including methods, types, and usage examples.

MMatt Silverlock https://developers.cloudflare.com/workflows/build/workers-api/#nonretryableerror

L

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

Oh nice thank you

L

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

I'm getting this error with the cloudflare blank starter repo when I change the index.ts to use workflows (the test passed before0

[vpw:inf] Starting isolated runtimes for vitest.config.mts...
Worker "workflows:telegram-mod-wf"'s binding "USER_WORKFLOW" refers to service "core:user:vitest-pool-workers-runner-" with a named entrypoint "MessageHandler", but "core:user:vitest-pool-workers-runner-" has no such named entrypoint.
WARN - IDE integration: Got finished tests before collecting them
WARN - IDE integration: Cannot finish not started testing

[vpw:inf] Starting isolated runtimes for vitest.config.mts...
Worker "workflows:telegram-mod-wf"'s binding "USER_WORKFLOW" refers to service "core:user:vitest-pool-workers-runner-" with a named entrypoint "MessageHandler", but "core:user:vitest-pool-workers-runner-" has no such named entrypoint.
WARN - IDE integration: Got finished tests before collecting them
WARN - IDE integration: Cannot finish not started testing

[vpw:inf] Starting isolated runtimes for vitest.config.mts...
Worker "workflows:telegram-mod-wf"'s binding "USER_WORKFLOW" refers to service "core:user:vitest-pool-workers-runner-" with a named entrypoint "MessageHandler", but "core:user:vitest-pool-workers-runner-" has no such named entrypoint.
WARN - IDE integration: Got finished tests before collecting them
WARN - IDE integration: Cannot finish not started testing

[vpw:inf] Starting isolated runtimes for vitest.config.mts...
Worker "workflows:telegram-mod-wf"'s binding "USER_WORKFLOW" refers to service "core:user:vitest-pool-workers-runner-" with a named entrypoint "MessageHandler", but "core:user:vitest-pool-workers-runner-" has no such named entrypoint.
WARN - IDE integration: Got finished tests before collecting them
WARN - IDE integration: Cannot finish not started testing

L

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

can someone help with this one please? not sure if it's an issue on my side or CF. it's just a log and everything else works fine but it seems a bit weird. it has something to do with workflows so should have posted it here I guess workers-and-pages-helpWeird "run" error with workers + CF workflows

J

jordanfinners•1/14/25, 7:19 AM

Hey, I think I've got a bug.

Every so often workflows will fail to find the toISOString method on the WorkflowEvent.

timestamp.toISOString is not a function

timestamp.toISOString is not a function

timestamp.toISOString is not a function

timestamp.toISOString is not a function

Which leads me to belive sometimes it's not parsing the event into a date object or losing that method somewhere.

Its failed 10 workflows for me overnight

J

jordanfinners•1/14/25, 9:18 AM

@Skye yes sure

export class ActionsWorkflow extends WorkflowEntrypoint<Env, StockTakeActionEvent> {
async run(event: WorkflowEvent<StockTakeActionEvent>, step: WorkflowStep) {
// some other code, but doesn't interact with event
const timestamp = event.timestamp.toISOString()
}
}

K

kchro3•1/14/25, 8:14 PM

Hi, folks, would there be a problem with using a for loop over a step.do & a step.sleep?

for example:

const configs = [{ id: 1, delay: "2 hours" }, { ... }]
for config in configs:
  await step.do(`do ${config.id}`, { ... })
  await step.sleep(`sleep ${config.id}`, config["delay"])

const configs = [{ id: 1, delay: "2 hours" }, { ... }]
for config in configs:
  await step.do(`do ${config.id}`, { ... })
  await step.sleep(`sleep ${config.id}`, config["delay"])

const configs = [{ id: 1, delay: "2 hours" }, { ... }]
for config in configs:
  await step.do(`do ${config.id}`, { ... })
  await step.sleep(`sleep ${config.id}`, config["delay"])

const configs = [{ id: 1, delay: "2 hours" }, { ... }]
for config in configs:
  await step.do(`do ${config.id}`, { ... })
  await step.sleep(`sleep ${config.id}`, config["delay"])

i'm not sure how this works behind the scenes, but i read that the step names need to be static so that they will be cached, so i imagine that if the workflow shuts down after the first sleep, it will reiterate over configs but "skip" the steps

do 1

do 1

do 1

do 1 and

sleep 1

sleep 1

sleep 1

sleep 1 and pick up from

do 2

do 2

do 2

do 2. is that correct?

K

kchro3•1/14/25, 8:34 PM

just minor feedback, but it would be helpful if it was spelled out what happens on workflow reboots, especially in this section: https://developers.cloudflare.com/workflows/build/rules-of-workflows/#do-not-rely-on-state-outside-of-a-step

we were confused by the example because a for-loop has dynamic variables, so we weren't sure if we needed to store the index in the workflow state. there were other examples with for-loops but not with sleep calls that could force a hibernation.

Cloudflare Docs

Rules of Workflows · Cloudflare Workflows docs

A Workflow contains one or more steps. Each step is a self-contained, individually retriable component of a Workflow. Steps may emit (optional) state that allows a Workflow to persist and continue from that step, even if a Workflow fails due to a network or infrastructure issue.

Ssmcstewart Hey there, has anyone had any issues with `NonRetryableError()`? it just doesn't...

M

Matt Silverlock•1/15/25, 3:26 PM

What version of wrangler are you using? How are you seeing that it is retrying the step?

I can't reproduce this with your exact code:

MMatt Silverlock What version of wrangler are you using? How are you seeing that it is retrying t...

M

Matt Silverlock•1/15/25, 3:27 PM

Fails every time, as expected:

Ssmcstewart @Matt Thanks! It's certainly a wrangler dev issue.

M

Matt Silverlock•1/15/25, 3:46 PM

You mean - only local dev? What version of wrangler?

L

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

I have some feedback – it seems that in a step.do() not the full error message may be shown on the dashboard? it just says ZodError; I doubt it's an issue on zod's side?

await step.do("detect spam", async () => {
  return await detectSpam(this.env, opts.payload.message.content);
});

await step.do("detect spam", async () => {
  return await detectSpam(this.env, opts.payload.message.content);
});

await step.do("detect spam", async () => {
  return await detectSpam(this.env, opts.payload.message.content);
});

await step.do("detect spam", async () => {
  return await detectSpam(this.env, opts.payload.message.content);
});

check spam basically does this:

    const response = await ai(env).chat.completions.create({
        response_format: zodResponseFormat(schema, "spam_detection"),
        model: "gpt-4o",
        messages: [
            {
                role: "user",
                content: prompt,
            },
        ],
    });

    return schema.parse(JSON.parse(response.choices[0].message.content || "{}"));

    const response = await ai(env).chat.completions.create({
        response_format: zodResponseFormat(schema, "spam_detection"),
        model: "gpt-4o",
        messages: [
            {
                role: "user",
                content: prompt,
            },
        ],
    });

    return schema.parse(JSON.parse(response.choices[0].message.content || "{}"));

    const response = await ai(env).chat.completions.create({
        response_format: zodResponseFormat(schema, "spam_detection"),
        model: "gpt-4o",
        messages: [
            {
                role: "user",
                content: prompt,
            },
        ],
    });

    return schema.parse(JSON.parse(response.choices[0].message.content || "{}"));

    const response = await ai(env).chat.completions.create({
        response_format: zodResponseFormat(schema, "spam_detection"),
        model: "gpt-4o",
        messages: [
            {
                role: "user",
                content: prompt,
            },
        ],
    });

    return schema.parse(JSON.parse(response.choices[0].message.content || "{}"));