they show up in workflow instance details page but top level errors are not retried.

Jjohtso how do I see logs from a workflow?

K

koraytaylanOP•5/20/25, 5:22 PM

you see them from the observability page where you track your worker logs also.

Kkoraytaylan they show up in workflow instance details page but top level errors are not retr...

J

johtso•5/20/25, 5:51 PM

they don't seem to appear on the workflow instance details page, the instance is marked as errored, but there are no steps to attach the error to so it isn't shown

J

johtso•5/20/25, 5:51 PM

my solution was to wrap everything in a top level step with no retries

Jjohtso they don't seem to appear on the workflow instance details page, the instance is...

K

koraytaylanOP•5/20/25, 5:54 PM

i am able to see the top level errors' messages on that page which i thought it would work the same for you sorry about that

Kkoraytaylan i am able to see the top level errors' messages on that page which i thought it ...

J

johtso•5/20/25, 5:59 PM

oh right, I do actually see something, but it just says "The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled"

J

johtso•5/20/25, 5:59 PM

it doesn't give me the error's message

C

charl.dev•5/21/25, 8:12 PM

On my paid workers account, it seems I can’t deploy a worker with workflows. When I try publish the worker, the worker does get deployed but wrangler throws error for the ../workflows api.

Auth error

I also get an error if I try wrangler workflows list

C

charl.dev•5/21/25, 8:12 PM

I’ve tried logging in and out

C

charl.dev•5/21/25, 8:12 PM

Do I need to be enabled for workflows?

B

Boragorn•5/22/25, 1:45 AM

@moonage.dev not sure if this is what you're looking for, but that's how I deploy workers with workflows:

// src/workers/my.worker.ts

import { MyWorkflow } from "../workflows/my.workflow";

export {
   MyWorkflow
};


type Bindings = {
  MY_WORKFLOW: Workflow;
};

const app = new Hono<{ Bindings: Bindings }>();

app.post('/', async (c) => {
  return c.env.MY_WORKFLOW.create(..);
}) 

export default {
  fetch: app.fetch,
};

// src/workers/my.worker.ts

import { MyWorkflow } from "../workflows/my.workflow";

export {
   MyWorkflow
};


type Bindings = {
  MY_WORKFLOW: Workflow;
};

const app = new Hono<{ Bindings: Bindings }>();

app.post('/', async (c) => {
  return c.env.MY_WORKFLOW.create(..);
}) 

export default {
  fetch: app.fetch,
};

// src/workers/my.worker.ts

import { MyWorkflow } from "../workflows/my.workflow";

export {
   MyWorkflow
};


type Bindings = {
  MY_WORKFLOW: Workflow;
};

const app = new Hono<{ Bindings: Bindings }>();

app.post('/', async (c) => {
  return c.env.MY_WORKFLOW.create(..);
}) 

export default {
  fetch: app.fetch,
};

// src/workers/my.worker.ts

import { MyWorkflow } from "../workflows/my.workflow";

export {
   MyWorkflow
};


type Bindings = {
  MY_WORKFLOW: Workflow;
};

const app = new Hono<{ Bindings: Bindings }>();

app.post('/', async (c) => {
  return c.env.MY_WORKFLOW.create(..);
}) 

export default {
  fetch: app.fetch,
};

C

charl.dev•5/22/25, 6:30 AM

It’s not a problem with the worker, tried to deploy a fresh workflow starter and same issue:

workflows-starter2 % npm run deploy

workflows-starter@0.0.1 deploy
wrangler deploy

wrangler 4.16.0
-------------------

Total Upload: 2.20 KiB / gzip: 1.02 KiB
Your Worker has access to the following bindings:

Workflows:
- MY_WORKFLOW: MyWorkflow
  Uploaded workflows-starter2 (8.26 sec)

✘ [ERROR] A request to the Cloudflare API (/accounts/xxx/workflows/workflows-starter) failed.

Authentication error [code: 10000]

Getting User settings...

You are logged in with an OAuth Token, associated with the email xxx@gmail.com.
┌───────────────────────────────┬──────────────────────────────────┐
│ Account Name │ Account ID │
├───────────────────────────────┼──────────────────────────────────┤
│ xxx@gmail.com's Account │ xxx │
└───────────────────────────────┴──────────────────────────────────┘

Token Permissions: If scopes are missing, you may need to logout and re-login.
Scope (Access)

account (read)
user (read)
workers (write)
workers_kv (write)
workers_routes (write)
workers_scripts (write)
workers_tail (read)
d1 (write)
pages (write)
zone (read)
ssl_certs (write)
ai (write)
queues (write)
pipelines (write)
secrets_store (write)
offline_access
Membership roles in "xxx@gmail.com's Account": Contact account super admin to change your permissions.
Super Administrator - All Privileges

S

Stupefystar•5/22/25, 6:33 AM

Can someone please tell me why my workflows are running multiples times in parallel?

export default {
    async fetch(req: Request, env: Env): Promise<Response> {
        let instance = await env.DATA_WORKFLOW.create();
        return Response.json({
            id: instance.id,
            details: await instance.status(),
        });
    },
};

export default {
    async fetch(req: Request, env: Env): Promise<Response> {
        let instance = await env.DATA_WORKFLOW.create();
        return Response.json({
            id: instance.id,
            details: await instance.status(),
        });
    },
};

export default {
    async fetch(req: Request, env: Env): Promise<Response> {
        let instance = await env.DATA_WORKFLOW.create();
        return Response.json({
            id: instance.id,
            details: await instance.status(),
        });
    },
};

export default {
    async fetch(req: Request, env: Env): Promise<Response> {
        let instance = await env.DATA_WORKFLOW.create();
        return Response.json({
            id: instance.id,
            details: await instance.status(),
        });
    },
};

I will have

do something with ids

do something with ids

do something with ids

do something with ids run multiple times even tho it doesn't fail or anything

async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
        const storageKey = `instructions-${event.instanceId}.json`;
        const defaultConfig = {retries: { limit: 1, delay: 1000 }};

        try {
            const ids = await step.do('download ids', defaultConfig, async () => {
                //
            });

            await step.do('do something with ids', defaultConfig, async () => {
                //
            });

            await step.do('do something with ids', defaultConfig, async () => {
                //
            });

            // Cleanup after successful completion
            await this.env.TEMP_STORAGE.delete(storageKey);
        } catch (error) {
            // Cleanup on failure
            await this.env.TEMP_STORAGE.delete(storageKey);
            throw new NonRetryableError("Unknown error");
        }

        let workflow = await this.env.DATA_WORKFLOW.get(event.instanceId);
        await workflow.terminate();
    }

async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
        const storageKey = `instructions-${event.instanceId}.json`;
        const defaultConfig = {retries: { limit: 1, delay: 1000 }};

        try {
            const ids = await step.do('download ids', defaultConfig, async () => {
                //
            });

            await step.do('do something with ids', defaultConfig, async () => {
                //
            });

            await step.do('do something with ids', defaultConfig, async () => {
                //
            });

            // Cleanup after successful completion
            await this.env.TEMP_STORAGE.delete(storageKey);
        } catch (error) {
            // Cleanup on failure
            await this.env.TEMP_STORAGE.delete(storageKey);
            throw new NonRetryableError("Unknown error");
        }

        let workflow = await this.env.DATA_WORKFLOW.get(event.instanceId);
        await workflow.terminate();
    }

async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
        const storageKey = `instructions-${event.instanceId}.json`;
        const defaultConfig = {retries: { limit: 1, delay: 1000 }};

        try {
            const ids = await step.do('download ids', defaultConfig, async () => {
                //
            });

            await step.do('do something with ids', defaultConfig, async () => {
                //
            });

            await step.do('do something with ids', defaultConfig, async () => {
                //
            });

            // Cleanup after successful completion
            await this.env.TEMP_STORAGE.delete(storageKey);
        } catch (error) {
            // Cleanup on failure
            await this.env.TEMP_STORAGE.delete(storageKey);
            throw new NonRetryableError("Unknown error");
        }

        let workflow = await this.env.DATA_WORKFLOW.get(event.instanceId);
        await workflow.terminate();
    }

async run(event: WorkflowEvent<Params>, step: WorkflowStep) {
        const storageKey = `instructions-${event.instanceId}.json`;
        const defaultConfig = {retries: { limit: 1, delay: 1000 }};

        try {
            const ids = await step.do('download ids', defaultConfig, async () => {
                //
            });

            await step.do('do something with ids', defaultConfig, async () => {
                //
            });

            await step.do('do something with ids', defaultConfig, async () => {
                //
            });

            // Cleanup after successful completion
            await this.env.TEMP_STORAGE.delete(storageKey);
        } catch (error) {
            // Cleanup on failure
            await this.env.TEMP_STORAGE.delete(storageKey);
            throw new NonRetryableError("Unknown error");
        }

        let workflow = await this.env.DATA_WORKFLOW.get(event.instanceId);
        await workflow.terminate();
    }

Ccharl.dev It’s not a problem with the worker, tried to deploy a fresh workflow starter and...

C

charl.dev•5/22/25, 6:35 AM

Magically working now to deploy

Original message was deleted

S

Stupefystar•5/22/25, 9:19 AM

I simplified it for the demo, but each one has their own unique name.

S

Stupefystar•5/22/25, 9:20 AM

ie first step runs this command where it runs 3 times all at once but this should only be run once.

S

Stupefystar•5/22/25, 9:20 AM

Sometime it'll run once, sometimes three times

S

Stupefystar•5/22/25, 9:59 AM

S

Stupefystar•5/22/25, 9:59 AM

just within the closure of the first step

S

Stupefystar•5/22/25, 10:57 AM

AHHH i am an idiot.. so because the web server is calling

fetch(req: Request, env: Env): Promise<Response>

fetch(req: Request, env: Env): Promise<Response>

fetch(req: Request, env: Env): Promise<Response>

fetch(req: Request, env: Env): Promise<Response> for the root, and the favicon requests that explains why each step is being called multiple times.

WWallslide Is it the env.WORKFLOW.create call that is failing? Is it in the workflow's run(...

C

Chaika•5/22/25, 7:26 PM

nothing's failing, it's just the way workflow runs show in logs

C

Chaika•5/22/25, 7:28 PM

team said they working on fixing workflows
https://discord.com/channels/595317990191398933/1303411588929294358/1303488051917492318

S

scook•5/22/25, 11:50 PM

^ Does this mean there's an ongoing incident right now? Because some of my workflow invocations failed to call

await env.WORKFLOW_NAME.create()

await env.WORKFLOW_NAME.create()

await env.WORKFLOW_NAME.create()

await env.WORKFLOW_NAME.create() with an ambiguous "internal error", whereas some succeeded.

S

scook•5/22/25, 11:58 PM

@Luís Duarte

Is there anything I can do to troubleshoot? We have certain invocations succeeding and others throwing

"Error: internal error"

"Error: internal error"

"Error: internal error"

"Error: internal error" as far as I can tell.

M

Marco Aleixo•5/23/25, 3:30 PM

[32mdetails:[0m { "request_id": "ae65c446-f13d-4f95-98b8-ed25ccfa47e6", "fileId": "a386a543-91f9-4a78-af85-257ee4ba2728", "error": "internal error", "stack": "Error: internal error\n at callFetcher (cloudflare-internal:workflows-api:24:15)\n at async WorkflowImpl.create (cloudflare-internal:workflows-api:78:24)\n at async fileUploadService (main.js:919559:11)\n at async fileUploadController (main.js:919663:32)\n at async dispatch (main.js:1116:21)\n at async main.js:859416:9\n at async dispatch (main.js:1116:21)\n at async main.js:859416:9\n at async dispatch (main.js:1116:21)\n at async main.js:967997:5" }",

[32mdetails:[0m { "request_id": "ae65c446-f13d-4f95-98b8-ed25ccfa47e6", "fileId": "a386a543-91f9-4a78-af85-257ee4ba2728", "error": "internal error", "stack": "Error: internal error\n at callFetcher (cloudflare-internal:workflows-api:24:15)\n at async WorkflowImpl.create (cloudflare-internal:workflows-api:78:24)\n at async fileUploadService (main.js:919559:11)\n at async fileUploadController (main.js:919663:32)\n at async dispatch (main.js:1116:21)\n at async main.js:859416:9\n at async dispatch (main.js:1116:21)\n at async main.js:859416:9\n at async dispatch (main.js:1116:21)\n at async main.js:967997:5" }",

[32mdetails:[0m { "request_id": "ae65c446-f13d-4f95-98b8-ed25ccfa47e6", "fileId": "a386a543-91f9-4a78-af85-257ee4ba2728", "error": "internal error", "stack": "Error: internal error\n at callFetcher (cloudflare-internal:workflows-api:24:15)\n at async WorkflowImpl.create (cloudflare-internal:workflows-api:78:24)\n at async fileUploadService (main.js:919559:11)\n at async fileUploadController (main.js:919663:32)\n at async dispatch (main.js:1116:21)\n at async main.js:859416:9\n at async dispatch (main.js:1116:21)\n at async main.js:859416:9\n at async dispatch (main.js:1116:21)\n at async main.js:967997:5" }",

[32mdetails:[0m { "request_id": "ae65c446-f13d-4f95-98b8-ed25ccfa47e6", "fileId": "a386a543-91f9-4a78-af85-257ee4ba2728", "error": "internal error", "stack": "Error: internal error\n at callFetcher (cloudflare-internal:workflows-api:24:15)\n at async WorkflowImpl.create (cloudflare-internal:workflows-api:78:24)\n at async fileUploadService (main.js:919559:11)\n at async fileUploadController (main.js:919663:32)\n at async dispatch (main.js:1116:21)\n at async main.js:859416:9\n at async dispatch (main.js:1116:21)\n at async main.js:859416:9\n at async dispatch (main.js:1116:21)\n at async main.js:967997:5" }",

When I start to get high traffic in an endpoint I'm starting to see errors above when trying to call a Workflow.
Seems to be something internal on CF side, the same code works fine when the traffic is "low"

And when I say high traffic, I'm saying something like 6 requests/s, in theory, this is supposed to be a low traffic on CF scale, right?

A

ac•5/24/25, 12:13 AM

Is it possible to get the number of times a workflow step has retried? I'd like to call some code on the final retry to prevent future jobs from picking up the same item.

I know I could technically keep it in a variable outside of the step but I worry that context would be lost on retries. Any options?

K

koraytaylanOP•5/24/25, 3:39 PM

in workflow instance details page, output gets truncated for a particular "step history" which is a problem for me. i wonder if there is any plans to change this behavior?

M

Mr. Technician•5/24/25, 4:35 PM

I have a question the docs are not clear on:

// ✅ Good: steps that are dynamically named are constructed in a deterministic way.
    // In this case, `catList` is a step output, which is stable, and `catList` is
    // traversed in a deterministic fashion (no shuffles or random accesses) so,
    // it's fine to dynamically name steps (e.g: create a step per list entry).
    let catList = await step.do("get cat list from KV", async () => {
      return await env.KV.get("cat-list");
    });

    for (const cat of catList) {
      await step.do(`get cat: ${cat}`, async () => {
        return await env.KV.get(cat);
      });
    }

// ✅ Good: steps that are dynamically named are constructed in a deterministic way.
    // In this case, `catList` is a step output, which is stable, and `catList` is
    // traversed in a deterministic fashion (no shuffles or random accesses) so,
    // it's fine to dynamically name steps (e.g: create a step per list entry).
    let catList = await step.do("get cat list from KV", async () => {
      return await env.KV.get("cat-list");
    });

    for (const cat of catList) {
      await step.do(`get cat: ${cat}`, async () => {
        return await env.KV.get(cat);
      });
    }

// ✅ Good: steps that are dynamically named are constructed in a deterministic way.
    // In this case, `catList` is a step output, which is stable, and `catList` is
    // traversed in a deterministic fashion (no shuffles or random accesses) so,
    // it's fine to dynamically name steps (e.g: create a step per list entry).
    let catList = await step.do("get cat list from KV", async () => {
      return await env.KV.get("cat-list");
    });

    for (const cat of catList) {
      await step.do(`get cat: ${cat}`, async () => {
        return await env.KV.get(cat);
      });
    }

// ✅ Good: steps that are dynamically named are constructed in a deterministic way.
    // In this case, `catList` is a step output, which is stable, and `catList` is
    // traversed in a deterministic fashion (no shuffles or random accesses) so,
    // it's fine to dynamically name steps (e.g: create a step per list entry).
    let catList = await step.do("get cat list from KV", async () => {
      return await env.KV.get("cat-list");
    });

    for (const cat of catList) {
      await step.do(`get cat: ${cat}`, async () => {
        return await env.KV.get(cat);
      });
    }

Can I store the looped returned values? If so, how can I do so deterministically?

MMr. Technician I have a question the docs are not clear on: ```ts // ✅ Good: steps that are dy...

K

koraytaylanOP•5/24/25, 5:34 PM

in the workflow rules page there was an example to that. the correct way was to use

Promise.all

Promise.all

Promise.all

Promise.allif i recall correctly.

Kkoraytaylan in the workflow rules page there was an example to that. the correct way was to ...

M

Mr. Technician•5/24/25, 5:35 PM

that example is different though, it used a known number of steps (2 in the example)

M

Mr. Technician•5/24/25, 5:35 PM

unless I can just slap this loop into a promise.all?

M

Mr. Technician•5/24/25, 5:35 PM

I'm more experienced with Tasks in C# than promises

MMr. Technician that example is different though, it used a known number of steps (2 in the exam...

K

koraytaylanOP•5/24/25, 5:46 PM

ok i see your point. to store the returned items you need to do,

const cats = await Promise.all(catList.map(cat => step.do(`get cat: ${cat}`, () => env.KV.get(cat))));

const cats = await Promise.all(catList.map(cat => step.do(`get cat: ${cat}`, () => env.KV.get(cat))));

const cats = await Promise.all(catList.map(cat => step.do(`get cat: ${cat}`, () => env.KV.get(cat))));

const cats = await Promise.all(catList.map(cat => step.do(`get cat: ${cat}`, () => env.KV.get(cat))));

this should work

Kkoraytaylan ok i see your point. to store the returned items you need to do, ```const cats =...

M

Mr. Technician•5/24/25, 8:14 PM

I'll give it a try, thanks

M

Marco Aleixo•5/24/25, 11:53 PM

I'm facing a lot of

A call to blockConcurrencyWhile() in a Durable Object waited for too long. The call was canceled and the Durable Object was reset.

while seeing spikes on my file upload endpoint, and this is happening on something internal on my Workflows, and those errors seems to be not retriable, how fix this?

A

ac•5/26/25, 2:03 PM

I have some logic that returns from a Workflow

run

run

run

run function after 2 steps if it doesn't need to progress further -- not an error, just a situation where it doesn't need to continue. I'm not throwing an error, just returning an object with some data, but for some reason it seems like this is still showing in the workflow's worker logs as an "Error" (but it shows up correctly in the Workflow logs as "Completed" -- no error). Is there something specific I need to be returning from the

run

run

run

run function so it doesn't register as an error/Exception in the Worker?

Aac I have some logic that returns from a Workflow `run` function after 2 steps if i...

C

Chaika•5/26/25, 2:08 PM

It's just how they all show, team was working on a fix
workflows
https://discord.com/channels/595317990191398933/1303411588929294358/1303488051917492318

CChaika It's just how they all show, team was working on a fix https://discord.com/chann...

A

ac•5/26/25, 2:09 PM

Ah thank you, good to know. That message being 6 months old doesn't give me a ton of confidence

Aac Is it possible to get the number of times a workflow step has retried? I'd like ...

J

johtso•5/27/25, 12:13 AM

You can catch the error (meaning retries were exhausted), do whatever you need to do, then rethrow the error

A

alex (he/him)•5/27/25, 7:02 AM

Can I use a Tail Worker to handle logs from workflow steps?

A

alex (he/him)•5/27/25, 7:02 AM

It seems that the logs don't get send to the tail worker.

Aalex (he/him)It seems that the logs don't get send to the tail worker.

A

ac•5/27/25, 2:24 PM

The logs should be in the main worker that the workflow is attached to

D

ddsgadget•5/28/25, 7:29 AM

@alex (he/him) I have looked everywhere and can never find logs for any steps in a workflow. Maybe they are somewhere but I cant find them. This is single biggest weakness of workflows right now - logs are incredibly difficult to find for steps and this makes debugging them close to impossible. they should put the logs for each step on the actual step in the dashboard. This is what most other workflow platforms do - the logs for any workflow step are immediately visible in a UI for a step. i guess the only thing to do is send the logs to an outside service from each step, which make things complicated.

P

Paul Mihai•5/28/25, 9:54 AM

This may be a bit off topic but I have a question for CF techs - why don't you guys buy/partner with the n8n project and integrate it over your services? Technologically it looks like a marriage made in heaven! It's almost like they built it for cloudlfare!

they show up in workflow instance details page but top level errors are not retried.

Similar Threads

Similar Threads

Similar Threads