Cloudflare Developers•15mo ago

Do retries count as a separate invocation for billing?

CChief Do retries count as a separate invocation for billing?

Dmitry•10/26/24, 1:30 AM

I would imagine so

Dmitry•10/26/24, 1:31 AM

oh invocation... hmm good question

Dmitry•10/26/24, 1:33 AM

I hope concurrency controls are on the way! So we can say like.. only x workflows (per workflow type) can run concurrently

Dmitry•10/26/24, 1:35 AM

For example I think Resend limits API requests to like 40req/sec I think? So limiting the concurrency of a workflow that sends emails would be great

Dmitry•10/26/24, 1:36 AM

Would be cool if you could set concurrency at a step level too.. not just the overall workflow

sdr•10/26/24, 3:58 AM

The api docs for instance creation has a bug in the response shape. Result is a single object and not a collection like the docs suggest
https://developers.cloudflare.com/api/operations/wor-create-new-workflow-instance

Cloudflare API Documentation

Interact with Cloudflare's products and services via the Cloudflare API

tornado•10/26/24, 5:11 AM

Is it possible to have workflows defined in a pages worker?

Ttornado Is it possible to have workflows defined in a pages worker?

DanGamble•10/26/24, 7:24 AM

No, they're just workers at the moment. This is just my opinion but they likely will stay that way with the introduction of worker assets (https://developers.cloudflare.com/workers/static-assets/)

Cloudflare Docs

Static Assets | Cloudflare Workers docs

Create full-stack applications deployed to Cloudflare Workers.

DanGamble•10/26/24, 9:12 AM

With a nested step, if a nested step fails or needs to be retried, does that mean the outer step also fails/retries?

DanGamble•10/26/24, 9:13 AM

Also, love the "Rules of Workflows" piece of the documentation https://developers.cloudflare.com/workflows/build/rules-of-workflows/. Definitely helps understand things a lot more. Would love to see this kind of thing on all products. Especially DO's

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.

LordSilver•10/26/24, 11:13 AM

Workflows not available in the TF provider?

Cayter•10/26/24, 4:41 PM

is there no way to delete workflow...?

CCayter is there no way to delete workflow...?

fry69•10/26/24, 4:43 PM

Not currently it seems -> workflows

Ffry69 Not currently it seems -> https://discord.com/channels/595317990191398933/129692...

Cayter•10/26/24, 4:44 PM

oh thx...

Aajgeiss0702 (for billing) what counts as an invocation? does each step attempt count as an i...

ajgeiss0702•10/26/24, 6:57 PM

bump

makisuo•10/26/24, 10:03 PM

Workflows work fine for me in dev mode but deployed seem to never finish, eventhough the last expected step finished succesfully

makisuo•10/26/24, 10:09 PM

I am using EffectTS and for that reason am wrapping step.do to use it better with effect but dont really see how that could be the issue:

export const stepEffect = <A, E>(
    step: { do: (name: string, fn: () => Promise<any>) => Promise<any> },
    stepName: string,
    effectFn: Effect.Effect<A, E, never>,
): Effect.Effect<A, E, never> => {
    return Effect.promise(() => executeRpcWithCleanup(() => step.do(stepName, async () => Effect.runPromise(effectFn))))
}

export const stepEffect = <A, E>(
    step: { do: (name: string, fn: () => Promise<any>) => Promise<any> },
    stepName: string,
    effectFn: Effect.Effect<A, E, never>,
): Effect.Effect<A, E, never> => {
    return Effect.promise(() => executeRpcWithCleanup(() => step.do(stepName, async () => Effect.runPromise(effectFn))))
}

Mmakisuo I am using EffectTS and for that reason am wrapping step.do to use it better wit...

Isaac McFadyen•10/26/24, 10:41 PM

Your first step for troubleshooting should probably be to see if it works without EffectTS. I don't think anyone here uses EffectTS and so the amount of help we can give when that's involved is going to be limited

IIsaac McFadyen Your first step for troubleshooting should probably be to see if it works withou...

makisuo•10/26/24, 10:44 PM

yeah will remove some and troubleshoot a bit myself

Just wanted to see if someone had run into similar issues before.

Avi•10/27/24, 12:06 AM

how do workflow updates work?

Avi•10/27/24, 12:07 AM

like if i deploy a new version of the code

Avi•10/27/24, 2:13 AM

ah, i found a thread addressing my concerns here: workflows

Dmitry•10/27/24, 2:45 AM

Anyone try implementing workflows into a SvelteKit app yet?

Trying to figure out how to load a Workflow class in something other than the workflow-starter app (i.e -

src/index.ts

src/index.ts

file)

Beaconcha.in•10/27/24, 3:16 AM

Beaconcha.in•10/27/24, 3:19 AM

Avi•10/27/24, 5:16 AM

is it possible to define different workflows for different environments, like
env.Production
env.Production
vs
env.Preview
env.Preview
in
wrangler.toml
wrangler.toml
? it is!

Avi•10/27/24, 6:21 AM

lol

LLordSilver I guess that's a Cloudflare thing then, because your Worker would still be activ...

CanRau•10/27/24, 11:24 AM

Think they explain how it works here https://blog.cloudflare.com/workers-pricing-scale-to-zero

CCanRau Think they explain how it works here <https://blog.cloudflare.com/workers-pricin...

LordSilver•10/27/24, 2:34 PM

Yeah I remember this, but that's Workers, not Workflows

LordSilver•10/27/24, 2:34 PM

unless a Workflow runs on a Worker?

LLordSilver unless a Workflow runs on a Worker?

Isaac McFadyen•10/27/24, 2:40 PM

It does, yes.

Isaac McFadyen•10/27/24, 2:40 PM

In the Workers runtime anyway.

DDmitry Anyone try implementing workflows into a SvelteKit app yet? 👀 Trying to figure...

Matt Silverlock•10/27/24, 3:20 PM

Bind to a Workflow from your SvelteKit app and invoke it? The Workflow doesn’t have to be in the same script.

sdr•10/27/24, 11:05 PM

This error message is confusing to me, throwing a NonRetryableError means the error is handled by the CF workflows platform right?

The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled

The execution of the Workflow instance was terminated, as a step threw an NonRetryableError and it was not handled

sdr•10/27/24, 11:05 PM

So it is handled but its by CF and not me

Ssdr So it is handled but its by CF and not me

itsmatteomanf•10/27/24, 11:11 PM

I'd add a "[...] and it was not handled by user's Worklow code, so the Workflow failed.", that should explain it better.

sdr•10/27/24, 11:20 PM

Also spotted a bug in the docs / return type: workflows

sdr•10/27/24, 11:27 PM

Also whats the right way to setup local development of shared resources? If I have a pages & workers / workflows how do I share wrangler state between them?

I see a suggestion of getPlatformProxy but the docs are a bit confusing
https://github.com/cloudflare/cloudflare-docs/issues/16572

GitHub

How to share state of D1 and other products locally (workers and pa...

Proposed changes https://developers.cloudflare.com/workers/wrangler/api/#parameters-1 https://developers.cloudflare.com/d1/build-with-d1/local-development/#persist-data Subject Matter How to share ...

sdr•10/27/24, 11:49 PM

Also I notice that the step name listed in the history have an int appended to them. Im not adding that so wondering why its there / where its documented

SSid Chatterjee Hello world. So what did we think? Catching up on feedback

MissS•10/28/24, 4:45 AM

Did we ever hear confirmation on how pricing works?

I.e. separate steps don’t count as a separate invocation? What about retries? Are they a separate invocation etc

Jani•10/28/24, 9:51 AM

Couldn't find this in docs: by default, how does id reuse work in practice? As example see temporal id reuse policy

JJani Couldn't find this in docs: by default, how does id reuse work in practice? As e...

Seekerdasbatatas•10/28/24, 10:08 AM

All IDs are unique at the moment - why do you need ID reuse in workflows?

SSeekerdasbatatas All IDs are unique at the moment - why do you need ID reuse in workflows?

fry69•10/28/24, 10:14 AM

My guess would be e.g. automatic "Terminate if Running", restart a workflow with updated information and kill any running one? This can be done with other existing means of course if I understand the docs correctly, just not automatic.

Ffry69 My guess would be e.g. automatic "Terminate if Running", restart a workflow with...

Seekerdasbatatas•10/28/24, 10:15 AM

hum that's an interesting use case, I'll note it ^^

MissS•10/28/24, 10:39 AM

What happens if I just use a constant for all of my workflow IDs? Will it ensure that only one workflow is valid or will it programatically make deriviative IDs?

export const stepEffect = <A, E>( step: { do: (name: string, fn: () => Promise<any>) => Promise<any> }, stepName: string, effectFn: Effect.Effect<A, E, never>, ): Effect.Effect<A, E, never> => { return Effect.promise(() => executeRpcWithCleanup(() => step.do(stepName, async () => Effect.runPromise(effectFn)))) }

Do retries count as a separate invocation for billing?

Similar Threads

Similar Threads

Similar Threads