@Diogo Ferreira @Seekerdasbatatas since I’m travelling / in transit
@Diogo Ferreira @Seekerdasbatatas since I’m travelling / in transit
MHave you seen:
we’ll be adding this to wrangler soon, but it’s the same template
we’ll be adding this to wrangler soon, but it’s the same template
AMaybe storing something in KV as part of a step with the key being the workflow id, and having the 
fetch
CI have a platform which is something like Zapier. My user want to schedule their own CRONs. Like run this action every 5 minutes. Is this something I can do with workflows?
MCan you describe a little more about what you're trying to do? Workflows are great for multi-step / async tasks, but aren't themselves a "task scheduler" - you can use Durable Object Alarms, the Agents SDK (and the scheduling API), or even Cron Triggers to schedule tasks - incl. Workflows.
Gno I did not, I was under the impression templates were in the dashboard
CPretty much say my user has a workflow like:
Search for new concerts in Rome and email me if tickets are less than 50$- run it
every 6 hours
- run it
MI'd consider using an Agent - e.g. an Agent for each user + the Agent schedules a ticket-search Workflow that runs the search + validates prices + reports back
MThis isn't the same, but it's similar: each repo is associated with an Agent -> the Agent kicks a Workflow for each PR.
In your case, it's an Agent per user, and the Workflow is for a ticket-search (instead of a PR/code review):
In your case, it's an Agent per user, and the Workflow is for a ticket-search (instead of a PR/code review):
CYeah I'm looking at the agents api
Cthanks
CHey guys, Should I move all of my complex tasks in workers into workflows? so far it seems like it doesn’t have that much disadvantages aside from being a little bit complicated.
Gworkflows seem a lot more streamlined an maintainable then doing the tasks independently, especially if they involve multiple workers or services.
theres also some things unique like the r2 trigger that could be really usefull on its own
theres also some things unique like the r2 trigger that could be really usefull on its own
GI'm going to try and move one of my pipeline systems over and see how it goes, it looks promising
CYeah, that’s really attempting
Gthats why I am glad theres a template as a starting point , give me something to start with and migrate over the pieces
SHi, I've added a reproduction repo in this issue - https://github.com/cloudflare/workers-sdk/issues/8850
GitHub
Which Cloudflare product(s) does this pertain to? Other What versions & operating system are you using? wrangler v4.9.0 Please provide a link to a minimal reproduction https://github.com/Suman0...
HHello, is there any way to start multiple different workflows in batch ( using only one request ) I know we can start multiple invocation of the same workflow using the createBatch but IDK about different ones
Gas in a workflow invoking another workflow?
Ha worker invoking multiple workflows at the same time
GI haven't dug into it yet but you could just have it invoke the triggers for each right?
MCall
.create
DHI! Sorry for the inconvenience. Our edge runtime update that brings support for
instance.sendEventIs workflows now out of beta? OK to use in production?
JThe Cloudflare Blog
Workflows — a durable execution engine built directly on top of Workers — is now Generally Available. We’ve landed new human-in-the-loop capabilities, more scale, and more metrics: just what you need for a production-ready service.
MI'm running into a somewhat frustrating auth error when trying to trigger or list workflows via the
cloudflareSomewhat related to the above, is logging from workflows captured in the worker logs?
I have this in
I have this in
wrangler.jsonc
JHey, I think there might be a bug with Cloudflare Workers.
Whenever I update any binding (like a KV namespace) from the dashboard and deploy the changes, the binding for the Workflow gets removed automatically. This seems unintended and could cause issues during deployment.
Whenever I update any binding (like a KV namespace) from the dashboard and deploy the changes, the binding for the Workflow gets removed automatically. This seems unintended and could cause issues during deployment.
Jthis is happening after the GA of workflow
MIf you are mixing the dashboard + wrangler you can run into conditions like this - strongly recommend using one model to deploy. cc @Sid Chatterjee if we can make sure Workflows bindings stick here.
Jbut what if I am out of my work station and I need to urgently update some Vars, secrets etc. first thought will be to use dashboard from mobile.
Jhey guys how do I reduce my storage metric in workflows? I see that I have over 5GB of storage used (!!) and I do not need this but I don't see any option to delete old instances or even configure the workflow API to set a smaller retention period. Any ideas?
CSo I'm building a tool that runs a workflow when a file gets placed in an r2 bucket. All working well. I'm trying to build a dashboard to show the upload events, trigger retries, etc.. The problem I'm running into is that env.WORKFLOW.get(<instanceId>) doesn't work for me in dev. Is this intended?
MThis will be landing soon, but we don’t yet charge for storage.
MCan you show the code, and what does “doesn’t work” mean - what is the error message? What version of wrangler?
CI just updated wrangler to latest. The code snippet I posted just returns null when running locally.
MWhat code snippet?
MPost the actual code - a minimal reproduction.
C
thanks for the reply. Will tomorrow. Just got in bed.SJust got it working!! Awesome!! Thanks 
CSo after further investigation, it turns out any time the dev server reloads (any code change), every workflow instance disappears. This is really annoying. Is this expected?
You can repro with the workflows starter template easily.
Just run it, go to localhost:8787, record the instanceId and note that localhost:8787?instanceId=<id> shows details of the instance, add a console.log call anywhere and save, now localhost:8787?instanceId=<id> gives
You can repro with the workflows starter template easily.
npm create cloudflare@latest workflows-starter -- --template "cloudflare/workflows-starter"Just run it, go to localhost:8787, record the instanceId and note that localhost:8787?instanceId=<id> shows details of the instance, add a console.log call anywhere and save, now localhost:8787?instanceId=<id> gives
instance.not_found
AHello, do you have a cron mode for workflows? Let's say; start workflow A every 1st monday of the month?
FHi! Has anyone been able to get cross-script to work locally? I've seen other people encounter this issue but not seen any solutions
It works when called from the same worker, and service bindings between the workers seem to work fine, it's only an issue with the cross-script bindings.
✘ [ERROR] Worker "workflows:s3-update-status"'s binding "USER_WORKFLOW" refers to a service "core:user:integrations", but no such service is defined.It works when called from the same worker, and service bindings between the workers seem to work fine, it's only an issue with the cross-script bindings.
VWhen workflows are queued, is it normal behavior to not show the
paramsThat's normal: dev sessions don't persist by default (otherwise we'd be told we're filling up everyone's disk + clobbering test runs/local dev). What are you trying to solve across
wrangler devShow your
wranglerI mean, I think there's a big gap between never letting things expire and expiring everything for a single character code change anywhere in the project right?
And let me be clear, this is a single
Like one option is that you could have a TTL on workflow instances that defaulted to like a day or something?
And let me be clear, this is a single
wrangler devLike one option is that you could have a TTL on workflow instances that defaulted to like a day or something?
MI can't reproduce that in the same invocation (nor should I be able to): instances persist during the running
wrangler dev
MIf you change the code, that's a new invocation (reload of all state)
COh I wouldn't call that a new invocation, I only invoked it once.
MI understand where you're coming from, but I'm also explaining why this is the case
