Call `.create` as needed for each Workflow.
Call
.create as needed for each Workflow.
DHI! Sorry for the inconvenience. Our edge runtime update that brings support for
instance.sendEvent is unfortunately arriving late. It is currently in our staged release process, and should be out very soon. It will make an announcement here once it fully propagated.
DIs 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
cloudflare npm package …MSomewhat 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
CLike, for example, my kv data doesn't disappear on each invocation right?
MWill chat w/ the team about options to opt-in to persistency here
CWhy do instances?
MInstances aren't just state on disk (unlike KV pairs) - again, understand the frustration but not the same thing.
CI really like the products you all are putting out but it's frustrating how every product behaves differently in terms of local vs remote vs what is default and what's available. I know it's early days for workflows but just wanted to give the feedback.
CIs there a way to list recently invoked workflow instances in dev? I can use the api in prod but that doesn't work for dev.
FThese are the wrangler configs. the workflow is just a simple placeholder one for now with a console log and sleep, but it works like expected when called in the same worker. But the second i add the binding in the other worker it crashes, despite being able to connect using service bindings
MThanks - taking a look!
HWill this make only one request? If not, then there's a possibility that one of the requests might fail.
VI'm trying to list or terminate workflows (both via rest api and via dashboard) returns
HTTP 500/10001 workflows.api.error.internal_serverNow getting 503 service unavailable (7010 service unavailable)
VOk, any workflows action, even creating workflows from inside a worker (via binding) throws errors
MOne request per Workflow. You can retry any that fail (although that should be very rare). How would you expect this to be solved?
AWooo! Congrats on the launch excited for this
FGetting similar issues when using the Vitest Pool Workers lib for testing my workflow that's triggered by a Durable Object.
FLmk if you solve this, it has me stuck :kek:
Sis
envcongrats on the launch btw!
Mthis.env- ensuring you pass your
type as a parameter to your Workflow class: https://developers.cloudflare.com/workflows/build/workers-api/#workflowentrypointEnv
Cloudflare Docs
This guide details the Workflows API within Cloudflare Workers, including methods, types, and usage examples.
MCloudflare Docs
Send invoice when shopping cart is checked out and paid for
Sgood to know, thanks! don't think i saw this documented explicitly btw
