Ai'd want them tied to the worker i'm deploying with the main
wrangler.toml
FTo 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 shows the last deployed instance
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') when just testing around
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. before accessing it… it’s not mentioned in the docs, they will add itBI 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.
IDo remember that you still have the 1k subrequest limit that applies and that retries will be counted against this limit.
DHas multiple workflows with local wrangler been "fixed" yet? I can't see any issues in the
wrangler-sdk repo. Shall I create one if it's not been fixed? Not sure where the state of this bug would be kept
Dstill broken as of last night since i ran into it
DHmm maybe i'll process 10 at a time then
MI haven't seen this mentioned anywhere in the docs - I can't figure out if sleeping executions are counted towards the concurrency limit.
general-helpDo sleeping Workflows count towards the maximum concurrent execution limit?
general-helpDo sleeping Workflows count towards the maximum concurrent execution limit?
SIs there a way to have a monorepo of several workflows in one repository ?
Sis someone succeded with same setup as for workers?
MYes, but right now that is broken in local dev. Search this channel for “multiple Workflows”
SCan I add my workflow definition to my existing hono cloudflare worker that contains all my other api logic, or do I need to set this up as a new project?
MYes, you can add as bindings. Also, you can create an endpoint to manage your workflow by reaching your instance. You can start, pause or resume your workflow via that hono endpoint.
Dhi, trying to add workflows like this in wrangler.toml
i have it under a [[env.staging]]
if i have one i works but with two the worker failes to start
"The Workers runtime failed to start. There is likely additional logging output above."
there is no error in the log. what am i missing?
i have it under a [[env.staging]]
if i have one i works but with two the worker failes to start
"The Workers runtime failed to start. There is likely additional logging output above."
there is no error in the log. what am i missing?
DOk, seems like i posted to fast and there is an answer above. Bug in local dev(?) any timeframe in getting that in dev hands?
FCloudflare does not do ETAs
F:soontm:
Dhaha fair ^^
