Cloudflare Developers•8mo ago

this issue is recurring. fix: just keep trying the same command again and again till it succeeds.

this issue is recurring.
fix: just keep trying the same command again and again till it succeeds.

not ideal fix ofc

Ttyx this issue is recurring. fix: just keep trying the same command again and again ...

boop•5/11/25, 7:46 PM

Have you tried reauthing?

Tobias•5/12/25, 6:20 AM

Is it possible to set concurrency limits on a workflow?
Kind of like how Trigger.dev does it (https://trigger.dev/docs/queue-concurrency).

My use case is to use browser rendering in a workflow and not allow more than 1 run at a time for this workflow in order to not go above the limitations of the browser rendering product.

Trigger.dev

Welcome to the Trigger.dev docs - Trigger.dev

Find all the resources and guides you need to get started

Original message was deleted

Tobias•5/12/25, 12:44 PM

How soon is :soontm:? Weeks, months, years?

Ttyx I am getting a very confusing bug. I am getting. `Error: (workflow.not_found) Pr...

zhawtof•5/12/25, 3:17 PM

Now I'm running into this as well

(workflow.not_found) Provided Workflow does not exist

(workflow.not_found) Provided Workflow does not exist

in production.

Anyone on the Cloudflare team know what could be happening? Seems a few other people have run into this.

ddsgadget•5/12/25, 11:22 PM

I really like workflows, but just want to say that they are extremely difficult to debug, because the console.logs are not available anywhere. So all you see is the result of a step and have no insight into potential issues when something in the step goes wrong.

Jjason Request for better error messages on workflow runs. I see constant error messag...

ddsgadget•5/12/25, 11:27 PM

You are not alone. I've posted this issue on many ocassions. Workflow can run fine, but will show errors in the runs in the dashboard. Someone the other day commented that you must JSON stringify the response from each step and then JSON Parse it back in next step, if you want to get rid of these errors. I haven't tried it yet, and none of Cloudflare examples do this, but apparently that solves these errors.

Dddsgadget I really like workflows, but just want to say that they are extremely difficult ...

SakuraFC•5/13/25, 2:54 AM

Aren’t the logs available under the worker that instantiated the workflow? I think I was able to see them (scratches head and trying to remember)

Ttyx anyone else getting auth issues when trying to publish worker with workflows? `...

Ollie•5/13/25, 11:19 AM

You might be suffering similar to what we have in this ongoing thread: workflowsI am not sure what has happened with

scook•5/14/25, 12:01 AM

Are there any limitations for local development on workflows that might affect the accuracy of

env.WORKFLOW.get(id)

env.WORKFLOW.get(id)

?

After I invoke a long-running workflow in one codepath, a different codepath it sometimes cannot find that instance (i.e. I get

Error: instance.not_found

Error: instance.not_found

). I've been unable to find a pattern for repro, except that it seems the codepath that invokes the workflow can successfully call

get(id)

get(id)

later, even in a different instance of the worker; whereas some other codepath will always get

instance.not_found

instance.not_found

. I'm using the same binding for the same worker with the same workflow id.

johtso•5/14/25, 7:34 AM

I see one of the workflows examples shows waiting for a web hook event. How would you deal with the scenario of a web hook being received before the workflow begins waiting for it? Are events queued up in any way?

Jonathan•5/14/25, 1:15 PM

Are there any best practices for implementing a workflow that is used for starting and stopping third party services?

I was considering storing a lock in a durable object that states if the start workflow has already been executed you can only run the stop workflow but you still need to track the workflow instance id.

Aalgads I am running into an error for a step: Storage failure for e8202eb85a3fa02c5c2d9...

Ollie•5/14/25, 5:24 PM

Limits can be seen here: https://developers.cloudflare.com/workflows/reference/limits/, so maybe something like limit on persisted output from each step

johtso•5/14/25, 6:26 PM

Why do the docs say there is a 30 Retention limit for completed Workflow state.. but then also say it's stored for 7 days?

johtso•5/14/25, 6:38 PM

Is it not possible to get workflow logs or even see what step a workflow is currently on through the workers API, only the http API?

Avi•5/14/25, 7:05 PM

wrangler types

wrangler types

expected to generate types for workflows defined in

wrangler.toml

wrangler.toml

Avi•5/14/25, 7:47 PM

ah i see, it doesn't support per-env, but does support toplevel definition

Avi•5/14/25, 7:48 PM

also, what happens if i reuse a workflow ID? i know i'm not supposed to but...

AAvi also, what happens if i reuse a workflow ID? i know i'm not supposed to but...

Ollie•5/15/25, 7:46 AM

IDs must be unique for a workflow instance, so it will throw an error

Jjohtso Why do the docs say there is a 30 Retention limit for completed Workflow state.....

johtso•5/15/25, 2:11 PM

hmm, is this because being able to adjust retention for a workflow is "coming soon" so it's currently fixed at 7 days?

cg•5/15/25, 4:42 PM

Hi all!
I'm intersted in setting something up with Workflows, but I noticed on this page:
https://developers.cloudflare.com/workflows/build/trigger-workflows/

That:

Known issue: Restarting a Workflow via the restart() method is not currently supported and will throw an exception (error).

Known issue: Restarting a Workflow via the restart() method is not currently supported and will throw an exception (error).

Is this still true? It seems the page was last updated Feb 18 2025, but Workflows has been GA for a month or so now. Can anyone confirm if restart() still throws errors?

cg•5/15/25, 4:46 PM

Additionally, does

restart()

restart()

'ing an instance count to the 100 per 10 second liimit of the Maximum Workflow instance creation rate?

Cccarse So after further investigation, it turns out any time the dev server reloads (an...

Magic Greg•5/15/25, 4:59 PM

that's pretty painful indeed! @Matt Silverlock do you have any idea of whats going on?

Ccg Hi all! I'm intersted in setting something up with Workflows, but I noticed on t...

Diogo Ferreira•5/15/25, 5:01 PM

Indeed, restarting a Workflow instance is still not supported, and will throw an error when called.

cg•5/15/25, 6:08 PM

Okay, good to know @Diogo Ferreira
Do you expect restart()'ing an instance count to the 100 per 10 second liimit of the Maximum Workflow instance creation rate, once it is implemented?

Ccg Okay, good to know @Diogo Ferreira Do you expect restart()'ing an instance coun...

Diogo Ferreira•5/15/25, 6:53 PM

Probably not. Restarting will (should) only count towards the concurrency limits

cg•5/15/25, 7:02 PM

excellent. I'm sure it's already in the roadmap, but +1 to getting this implemented. It's probably the only thing keeping us from moving our pretty high volume workload over

ac•5/16/25, 1:36 AM

In the code that is calling env.WORKFLOW.create(), is there any way to wait for that workflow to complete to continue executing that code? (assume it's from another worker). I know I can call instance.status at some point after it's complete, but not sure how I know when that is, and I need some context from the workflow's result in this other spot before continuing.

I figure that I should probably restructure all of this at some point so that isn't necessary, was just trying to see if I could avoid restructuring too much of my code

Marco Aleixo•5/16/25, 3:05 AM

I would love to be able see logs per step in the step details view. Trying to find the step logs using Logs tab from Workers is not the best experience.

Aac In the code that is calling env.WORKFLOW.create(), is there any way to wait for ...

tadhglewis•5/16/25, 4:10 AM

There's probably ways (looping until status changes) but it isn't recommended. Workflows are entirely async and there's no guarantee how quickly they'll be completed.

Instead your Workflow should emit a webhook back to where you process "workflow complete" once it's completed.

gamarra2042•5/16/25, 3:14 PM

guys, when we're calling worflows from a worker request, they're going to be queued

gamarra2042•5/16/25, 3:15 PM

and there's no other worflow running that will catch into rate limit

gamarra2042•5/16/25, 3:15 PM

any idea?

andifined.dev•5/16/25, 5:31 PM

Hey guys I‘ve got a question regardinhg sub request Limits within workflows:

I‘m fetching Images from my database within a loop about 600 ids, but right around the 300 ids done Mark, the workflow stops failing because of the Internat subrequest limit of 1000 requests for paid plan. So I‘m wondering now would I can do different?

FoudreTower•5/16/25, 6:54 PM

@andifined.dev I heard the cloudflare team is working to remove the subrequests limit ?

FFoudreTower @andifined.dev I heard the cloudflare team is working to remove the subrequests ...

andifined.dev•5/16/25, 6:55 PM

Sounds Great but when?

Aandifined.dev Sounds Great but when?

andifined.dev•5/16/25, 6:55 PM

Think I have to integrate some Kind of sharding here

planet•5/16/25, 11:44 PM

do workflows have unlimited subrequests

oof2win2•5/18/25, 12:23 PM

hey there, i've previously created workflows on DB changes with CDC and i created them based on some form of unique ID within the DB that I always knew was going to be unique. previously, when i backfilled CDC (say due to an outage etc), the old workflows just didn't get created but the new ones did - which is what i wanted. now when i do that though the worker errors as it can't create the workflow. is this an intended breaking change or no?

Nimesh•5/19/25, 5:22 AM

Hi, is there a way to get the statuses of multiple workflows in a single request? We have a number of workflows that we’d like to be able to get the statuses of, without making multiple parallel calls.

johtso•5/19/25, 3:08 PM

how would I run a workflow when another workflow fails for whatever reason?

johtso•5/19/25, 3:09 PM

is there a concept of some kind of "finally" task?

Jjohtso how would I run a workflow when another workflow fails for whatever reason?

koraytaylan•5/20/25, 7:58 AM

i think you could implement an abstract base class (which your actual workflow inherits) and then you could encapsulate the logic to capture error in this base class and add a message into a queue. then another worker would trigger and start that other workflow.

Kkoraytaylan i think you could implement an abstract base class (which your actual workflow i...

johtso•5/20/25, 8:01 AM

I don't think that works for the case of retry limits being reached

Aandifined.dev Hey guys I‘ve got a question regardinhg sub request Limits within workflows: I...

koraytaylan•5/20/25, 8:02 AM

it is interesting. i didn't know about such limitation. how about:
your current workflow would just be a proxy that adds those 600ids into a queue as 600 messages. then you could configure a worker that would trigger for those messages and create a separate workflow that only work for an individual image instead of trying to process all 600 in one workflow.

Jjohtso I don't think that works for the case of retry limits being reached

koraytaylan•5/20/25, 8:10 AM

i have what i described in a simpler way to log detailed error messages on what went wrong. so, from the highest level if i am able catch an error and process it, then i guess it should be possible to trigger another workflow. now that i also realize you might not even need that queue because you could consider this part as a separate step to just trigger that other workflow.

Kkoraytaylan i have what i described in a simpler way to log detailed error messages on what ...

johtso•5/20/25, 8:13 AM

I'm thinking for example sending a customer an email if the order workflow terminates unsuccessful, and maybe refunding their payment. Catching errors doesn't let me know if the workflow was about to terminate / if there were still retries remaining. I could of course catch any unrecoverable errors, but that would still leave the retries exhausted case

koraytaylan•5/20/25, 8:14 AM

i have an idea, i have been working with workflows and one thing that i keep thinking is how great it would be to have a tab called "Logs" inside workflow instance that displays

console.log

console.log

messages emitted during that workflow run.

Jjohtso I'm thinking for example sending a customer an email if the order workflow termi...

koraytaylan•5/20/25, 8:17 AM

i believe there are two different scopes at play here. step scoped code gets retried when an error happens. but workflow scoped code does not have this. below is the abstract class i am talking about and the catch part here works only once.

`
export abstract class AbstractWorkflow<T, R> extends WorkflowEntrypoint<Env, T> {
  protected abstract getName(): string;
  protected abstract validateInput(input: T): void;
  protected abstract runStep(event: WorkflowEvent<T>, step: WorkflowStep): Promise<R>;

  async run(event: WorkflowEvent<T>, step: WorkflowStep): Promise<unknown> {
    console.log({
      message: `${this.getName()} started.`,
      level: "info",
      event,
    });
    try {
      this.validateInput(event.payload);
      const output = await this.runStep(event, step);
      console.log({
        message: `${this.getName()} completed.`,
        level: "info",
        event,
        output,
      });
      return output;
    } catch (error) {
      console.log({
        message: `${this.getName()} failed.`,
        level: "error",
        event,
        error,
      });
      throw error;
    }
  }
}

`
export abstract class AbstractWorkflow<T, R> extends WorkflowEntrypoint<Env, T> {
  protected abstract getName(): string;
  protected abstract validateInput(input: T): void;
  protected abstract runStep(event: WorkflowEvent<T>, step: WorkflowStep): Promise<R>;

  async run(event: WorkflowEvent<T>, step: WorkflowStep): Promise<unknown> {
    console.log({
      message: `${this.getName()} started.`,
      level: "info",
      event,
    });
    try {
      this.validateInput(event.payload);
      const output = await this.runStep(event, step);
      console.log({
        message: `${this.getName()} completed.`,
        level: "info",
        event,
        output,
      });
      return output;
    } catch (error) {
      console.log({
        message: `${this.getName()} failed.`,
        level: "error",
        event,
        error,
      });
      throw error;
    }
  }
}

Kkoraytaylan it is interesting. i didn't know about such limitation. how about: your current...

andifined.dev•5/20/25, 8:22 AM

But for my understanding that‘s the whole Point of using workflows. A Workflow has steps which get retried automatically on failure und I can define some Kind of process where each step depends on the steps before. So I don‘t unterstand why it‘s necessary to implement a workaround for functionality the product itself provides

Already implemented some Kind of workaround on my own to get around those Limits, but currently I‘m just waiting for Container compatibility because it‘s solving so much additional Problems I‘m having with workflows right know IMHO

` export abstract class AbstractWorkflow<T, R> extends WorkflowEntrypoint<Env, T> { protected abstract getName(): string; protected abstract validateInput(input: T): void; protected abstract runStep(event: WorkflowEvent<T>, step: WorkflowStep): Promise<R>; async run(event: WorkflowEvent<T>, step: WorkflowStep): Promise<unknown> { console.log({ message: `${this.getName()} started.`, level: "info", event, }); try { this.validateInput(event.payload); const output = await this.runStep(event, step); console.log({ message: `${this.getName()} completed.`, level: "info", event, output, }); return output; } catch (error) { console.log({ message: `${this.getName()} failed.`, level: "error", event, error, }); throw error; } } }

this issue is recurring. fix: just keep trying the same command again and again till it succeeds.

Similar Threads

Similar Threads

Similar Threads