The same Worker can export both the scheduled handler and the Workflow
The 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
Ayeah, there are also a couple of other things. I think it will get fixed soon (like the create locally needing an id)
Bis it possible to access env vars from inside workflows? e.g. to access db usually a token/url is needed that is saved in the env
IAccess is the same as a normal worker, but it requires a
this.I see, thank you!
Bin general are there any materials that show cases of proven practices that work well with workflows? i.e. is it better to keep interaction with the db inside the workflow or outside of the workflow in the worker itself. or more generally what actions are better to perform inside workflow vs. inside a regular worker?
AI made a workaround. Add the workflow items to a d1. Then a do sends it every 10 seconds to the workflow. Dripping it into it.
Would be great if we could just add that on step level of workflow level
Would be great if we could just add that on step level of workflow level
AJust though about it now. I could have created a workflow that goes thru the list and sleeps between each entry...
IThe less work each step makes, the better. Each step will be retried, persisting results from other steps, but not variables outside of those (so the variable assigned from a step return is maintained, a random variable is not)
IDo a db step, do a processing step (or even a per item processing, if it’s a loop and it’s not too long to go over the step limit)
IDo consider that you can nest steps, too. If you were to need that.
Bthank you
DIsn’t the step limit 250? So I have a step that return an object of 500 items and need to loop over each item to make another external api call and do further processing, I can’t have a nested step inside the for loop to process each item? Since it sounds like I’d hit the step limit
IExactly, yes. The limit is 255 steps.
