That approach should work. The for loop should be outside the step, that way you will benefit from t

That approach should work. The for loop should be outside the step, that way you will benefit from the persistancy of previous successful step executions, sparing on the API calls.

Recommendation. Give it a spin!

DDiogo Ferreira That approach should work. The for loop should be outside the step, that way you...

Gyurmatag•10/29/24, 7:18 PM

Okay, Thank you! But What about the maximum 256 steps? I will definitely have more than that. Does the paid tier have limits regarding the steps?

i40west•10/29/24, 9:17 PM

What is the function passed to

step.do

step.do

supposed to return? If I return anything at all from it, it causes the workflow to throw an exception after finishing successfully, every time, and I can't figure out what I'm doing wrong

zuegno•10/30/24, 3:59 AM

Hello, I'm really excited to try Workflows. I tried to add a Workflow to a Remix application. I used the Remix example Framework guide in the Pages docs. Got this error on wrangler deploy:

[ERROR] Your Worker depends on the following Workflows, which are not exported in your entrypoint file: DemgEventWorkflow.

  You should export these objects from your entrypoint, build/worker/index.js

[ERROR] Your Worker depends on the following Workflows, which are not exported in your entrypoint file: DemgEventWorkflow.

  You should export these objects from your entrypoint, build/worker/index.js

Any ideas on how to fix are appreciated!

zuegno•10/30/24, 4:01 AM

My worker is built in a

functions/[[path]].ts

functions/[[path]].ts

file that looks like:

import { createPagesFunctionHandler } from "@remix-run/cloudflare-pages";

// eslint-disable-next-line @typescript-eslint/ban-ts-comment
// @ts-ignore - the server build file is generated by `remix vite:build`
// eslint-disable-next-line import/no-unresolved
import * as build from "../build/server";

export const onRequest = createPagesFunctionHandler({ build });

import { createPagesFunctionHandler } from "@remix-run/cloudflare-pages";

// eslint-disable-next-line @typescript-eslint/ban-ts-comment
// @ts-ignore - the server build file is generated by `remix vite:build`
// eslint-disable-next-line import/no-unresolved
import * as build from "../build/server";

export const onRequest = createPagesFunctionHandler({ build });

zuegno•10/30/24, 4:20 AM

Project was started with https://developers.cloudflare.com/workers/frameworks/framework-guides/remix/

Cloudflare Docs

Remix | Cloudflare Workers docs

Create a Remix application and deploy it to Cloudflare Workers with Workers Assets.

DiamondDragon•10/30/24, 6:22 AM

noticing if you have a long output in the trace online it will go off screen (copy button disappears)

DiamondDragon•10/30/24, 6:23 AM

also, maybe I missed it, but I haven't figured out how to run a workflow that's been modified locally, as opposed to the one already deployed. Is this where we're at with the beta or did i miss how to?

Zzuegno Hello, I'm really excited to try Workflows. I tried to add a Workflow to a Remix...

Cayter•10/30/24, 7:25 AM

Remix with Vite currently relies on Wrangler's getPlatformProxy() that uses miniflare under the hood. This setup means Remix is running on Node.js and accessing the Env through HTTP getPlatformProxy().
By following this PR, you can leverage more features specifically designed for Cloudflare Workers, remix with cloudflare pages will have bumpy journey ahead

Run the following commands to set up your development environment:

```
remix vite:dev
```
```
remix vite:dev
```
on port 3000

wrangler dev --define "process.env.NODE_ENV:'production'" --log-level=info --port=3001 --test-scheduled app/worker.ts

wrangler dev --define "process.env.NODE_ENV:'production'" --log-level=info --port=3001 --test-scheduled app/worker.ts

Note:

worker.ts

worker.ts

should be ESM-based for Cloudflare Workers.

wrangler dev

wrangler dev

enables you to develop queues, crons, and workflows within

workerd

workerd

environment instead of NodeJS.

the error you're encountering is because

getPlatformProxy()

getPlatformProxy()

doesn’t work with workflows. If you have

[[workflows]]

[[workflows]]

in wrangler.toml, Miniflare will refer to it, resulting in the error

the development experience for a Vite-powered app has limitations, especially with newer features. This should improve once Vite v6 is released, and Wrangler is updated to support it

Zzuegno Hello, I'm really excited to try Workflows. I tried to add a Workflow to a Remix...

Matt Silverlock•10/30/24, 1:53 PM

You will need to deploy a Worker with your Workflow; you can’t bundle it into your Pages (Remix) app.

DiamondDragon•10/30/24, 4:12 PM

I'm getting a

Type instantiation is excessively deep and possibly infinite.

Type instantiation is excessively deep and possibly infinite.

in a step. I don't think it's a very complex type being returned

DDiamondDragon noticing if you have a long output in the trace online it will go off screen (co...

Diogo FerreiraOP•10/30/24, 5:24 PM

Thanks for reporting it!

Avi•10/30/24, 11:24 PM

is there support for scheduling a workflow to run periodically, like a cron job?

Avi•10/30/24, 11:24 PM

or would I use a worker with a cron trigger to initiate a workflow?

Avi•10/30/24, 11:24 PM

oh the docs address this, yes, nvm

Avi•10/30/24, 11:28 PM

ok in that case

Jacob•10/30/24, 11:28 PM

If you want to run it more often than once a minute, you could have your workflow schedule its next run rather than an external trigger. Would just need to jump-start it initially

Avi•10/30/24, 11:28 PM

what does the workflow concurrency limit mean? does that mean that if I have 5k scheduled, 100 will be initally scheduled to run, and as they conplete,m ore will be scheduled?

Avi•10/30/24, 11:28 PM

basically 100 max parallelism?

JJacob If you want to run it more often than once a minute, you could have your workflo...

Avi•10/30/24, 11:29 PM

my usecase is that i'd like to run code every night at midnight, and id love to NOT have to create a separate cloudflare worker with a

scheduled

scheduled

handler for this

Avi•10/30/24, 11:29 PM

just one instance of that code

Avi•10/30/24, 11:29 PM

essentially a global singleton

Jacob•10/30/24, 11:29 PM

The same Worker can export both the scheduled handler and the Workflow

Jacob•10/30/24, 11:30 PM

So it can all be in one .ts file

JJacob The same Worker can export both the scheduled handler and the Workflow

Avi•10/30/24, 11:30 PM

yeah, but that worker is actually just a DO stub wrapper

Jacob•10/30/24, 11:31 PM

wdym?

Avi•10/30/24, 11:31 PM

i guess we could do it there though

JJacob wdym?

Avi•10/30/24, 11:31 PM

i mean the "worker" is literally just the minimum boilerplate/wrapper to wrap a DO stub

Avi•10/30/24, 11:31 PM

but that doesnt mean we cant add a cron scheduled handler to it

Jacob•10/30/24, 11:33 PM

Yeah I’d just put the scheduled handler in the same worker that you’re wanting to trigger Workflows from

Jacob•10/30/24, 11:39 PM

Another trick I’ve found with crons (in general) that hit external APIs is to not schedule right at the top of the hour - some APIs I’ve used can actually slow down a bit because of everyone’s crons hitting them at the exact same time

skip•10/31/24, 4:37 AM

Can a workflow codebase co-exist inside a Pages repo?

Sskip 👋 Can a workflow codebase co-exist inside a Pages repo?

fry69•10/31/24, 4:41 AM

wrangler will deploy those to different entities in Cloudflare, so it should not matter where they reside on your side.

fry69•10/31/24, 4:42 AM

You might face problems linking such a repo from the dashboard though, maybe it still works with custom build commands?

Avi•10/31/24, 5:06 AM

it looks like

workerd

workerd

crashes when more than a single workflow is defined in

wrangler.toml

wrangler.toml

Avi•10/31/24, 5:08 AM

ah yeah i see this discussed above

AAvi it looks like `workerd` crashes when more than a single workflow is defined in `...

fry69•10/31/24, 5:09 AM

It should be possible to use separate

wrangler.toml

wrangler.toml

files in separate directories and invoke wrangler separately in those directories with npm scripts.

fry69•10/31/24, 5:10 AM

Maybe even go full monorepo

Ffry69 It should be possible to use separate `wrangler.toml` files in separate director...

Avi•10/31/24, 5:10 AM

but how would those get deployed?

Avi•10/31/24, 5:10 AM

i'd want them tied to the worker i'm deploying with the main

wrangler.toml

wrangler.toml

AAvi but how would those get deployed?

fry69•10/31/24, 5:10 AM

To different Cloudflare names/entities?

Avi•10/31/24, 5:11 AM

i'm not trying to change our deployed infra to workaround a wrangler bug lol

Avi•10/31/24, 5:11 AM

i'm just gonna comment one out at a time

AAvi it looks like `workerd` crashes when more than a single workflow is defined in `...

DiamondDragon•10/31/24, 5:30 AM

ugh i spent like an hour today trying to figure out why i could get the worker server to start... added a 2nd test workflow to play around

Avi•10/31/24, 5:33 AM

yeah it’s rough. imo they should have added a note in the changelog or something

DiamondDragon•10/31/24, 5:36 AM

is it possible to inspect a workflow triggered locally?

Avi•10/31/24, 5:36 AM

i’d also love to know this

DiamondDragon•10/31/24, 5:37 AM

running

nr wrangler workflows instances describe test latest

nr wrangler workflows instances describe test latest

shows the last deployed instance

Mm0c I have a question how workflows are "versioned' Lets say a workflow has 3 steps ...

fry69•10/31/24, 6:00 AM

Running workflows will not get updated of course, only freshly instantiated workflows will run the new deployed version.

[ERROR] Your Worker depends on the following Workflows, which are not exported in your entrypoint file: DemgEventWorkflow. You should export these objects from your entrypoint, build/worker/index.js

import { createPagesFunctionHandler } from "@remix-run/cloudflare-pages"; // eslint-disable-next-line @typescript-eslint/ban-ts-comment // @ts-ignore - the server build file is generated by `remix vite:build` // eslint-disable-next-line import/no-unresolved import * as build from "../build/server"; export const onRequest = createPagesFunctionHandler({ build });

That approach should work. The for loop should be outside the step, that way you will benefit from t

Similar Threads

Similar Threads

Similar Threads