You will need to deploy a Worker with your Workflow; you can’t bundle it into your Pages (Remix) app
You will need to deploy a Worker with your Workflow; you can’t bundle it into your Pages (Remix) app.
DI'm getting a
Type instantiation is excessively deep and possibly infinite. in a step. I don't think it's a very complex type being returned
DThanks for reporting it!
Ais there support for scheduling a workflow to run periodically, like a cron job?
Aor would I use a worker with a cron trigger to initiate a workflow?
Aoh the docs address this, yes, nvm
Aok in that case
JIf 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
Awhat 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?
Abasically 100 max parallelism?
Amy 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
scheduledjust one instance of that code
Aessentially a global singleton
JThe same Worker can export both the scheduled handler and the Workflow
JSo it can all be in one .ts file
Ayeah, but that worker is actually just a DO stub wrapper
Jwdym?
Ai guess we could do it there though
Abut that doesnt mean we cant add a cron scheduled handler to it
JYeah I’d just put the scheduled handler in the same worker that you’re wanting to trigger Workflows from
JAnother 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
S
Can a workflow codebase co-exist inside a Pages repo?
Fwrangler will deploy those to different entities in Cloudflare, so it should not matter where they reside on your side.
FYou might face problems linking such a repo from the dashboard though, maybe it still works with custom build commands?
Ait looks like
workerdwrangler.tomlah yeah i see this discussed above
FIt should be possible to use separate
wrangler.tomlMaybe even go full monorepo 
Abut how would those get deployed?
Ai'd want them tied to the worker i'm deploying with the main
wrangler.tomlTo different Cloudflare names/entities?
Ai'm not trying to change our deployed infra to workaround a wrangler bug lol
Ai'm just gonna comment one out at a time
Dugh 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
Ayeah it’s rough. imo they should have added a note in the changelog or something
Dis it possible to inspect a workflow triggered locally?
Ai’d also love to know this
Drunning
nr wrangler workflows instances describe test latest
FRunning workflows will not get updated of course, only freshly instantiated workflows will run the new deployed version.
DNot sure if this is silly - does it make ense to use a RPC service binding in a workflow/step? getting
TypeError: Cannot read properties of undefined (reading 'TEST_SERVICE') 
Bis workflows accessible/supported from inside pages functions?
BI mean directly via env.[workflow_name] e.g. from astro project. i.e. not via network like fetch(...)
AI can't seem to figure out, how do I limit the amount of instances per minute a workflow can ingest? I have browser rendering working inside of the workflows and I want to limit it to only do around 1 instance per 10 seconds orso
Ban attempt to delete a workflow from the cli results in an error saying it failed. in the dashboard I have already deleted connected worker but the workflow itself doesn't get deleted regardless of how many times I try to delete it by way of
Bwhy then do they keep this in their docs. thank you for pionting it out though
FNobody told the docu team I guess
Aits a beta... just opened up... lets be kind that they didn't wait till everything was polished
FOf course, but it's been a few days since it is officially known, they could have added a note that this is currently not supported IMHO, esp. since this is so prominently mentioned in the docs
