heya, is there any estimate on increasing the concurrency of workflows?
heya, is there any estimate on increasing the concurrency of workflows?
ITLDR: not really, it's planned but no ETA
Omake sense ty
SIs the error happening with new instances?
SAh I see, can you give me your account id? I'll escalate this up
SIf you prefer yes, but account ids are safe to share publicly
LA workflow that was working fine is now erroring out with only this:
TypeError: The RPC receiver does not implement the method "run".
What could cause this given that it was working hours ago?
TypeError: The RPC receiver does not implement the method "run".
What could cause this given that it was working hours ago?
DSorry to hear that Lucas. Can you please share your account id for our team to take a look into it?
Lfacce5f30267ea8a9773949bfae2feff
DThank you
LSorted now, thanks to Diogo.
DJust to recap, and for reference if anyone face an identical issue, this was caused because the wrangler.toml file didn't contain the necessary definition
Ait looks like the average wall time displayed in the dashboard is waaaay off
Anot end-of-the-world stuff, but a bit odd 
Aand it displays a different, also wrong, number in the Metrics tab
A
D
Sorry about bumping this one again, but I’m stumped.Is there a way to see if I’m somehow bumping up against limits? The actual processing time shouldn’t be significant here. The network requests may be a bit slow, but from what I can gather from the docs, waiting on IO shouldn’t affect the limits.
Any insights or debugging advice would be appreciated.
LUnfortunately, that was not the cause. Same issue is happening again even though no changes have been made.
MCan you share more details? What does the full error message return? Just connection error? How many concurrent Workflows are running?
Shey everyone, I've done on my free time a batteries-included library for Workflows called Flowcesinha: https://github.com/LuisDuarte1/flowcesinha
- Custom storage engines and lazy step results (R2 included) so that, you can store more state inside of an step (and you can bring your own storage engine!);
- Error reporting (Sentry provided in flowcesinha-sentry) and Workflow failure handler;
- Reversable steps: ability to add a revert callback in case that the workflow fails;
- Durable fetch: ability to fetch from APIs with dynamic retries (that come from the Retry-After header);
- Functional primitives: doMap (map but every call is done inside of a step);
- ... more to come soon!
GitHub
A utility libraries for Cloudflare Workflows. Contribute to LuisDuarte1/flowcesinha development by creating an account on GitHub.
Fwooah! that's literally my wishlist for workflows, thank you for your work!
FI know you did that in your free time, and I really appreciate it, i'll be using it, but can we expect these features to be built-in in the future? 
ICloudflare Docs
Enable your Worker to be executed on a schedule.
I
Bhi team, I am struggling with creating/accessing database and service bindings for a workflow. Even though the bindings are defined in the wrangler.toml, the only binding that is accessible during the deployment is the workflow binding, DB and AGENT_LOOP are undefined.
wrangler.toml:
[[workflows]]
name = "wf-ainf-run-snap"
binding = "RUN_SNAP_WORKFLOW"
class_name = "RunSnapWorkflow"
main = "src/index.ts"
compatibility_date = "2024-01-01"
compatibility_flags = ["nodejs_compat"]
[[d1_databases]]
binding = "DB"
database_name = "ainfiltrators"
database_id = "xxxxx"
[[services]]
binding = "AGENT_LOOP"
service = "agent-loop"
deploy output:
Your worker has access to the following bindings:
thanks in advance!
wrangler.toml:
[[workflows]]
name = "wf-ainf-run-snap"
binding = "RUN_SNAP_WORKFLOW"
class_name = "RunSnapWorkflow"
main = "src/index.ts"
compatibility_date = "2024-01-01"
compatibility_flags = ["nodejs_compat"]
[[d1_databases]]
binding = "DB"
database_name = "ainfiltrators"
database_id = "xxxxx"
[[services]]
binding = "AGENT_LOOP"
service = "agent-loop"
deploy output:
Your worker has access to the following bindings:
- Workflows:
- RUN_SNAP_WORKFLOW: RunSnapWorkflow
thanks in advance!
HThis looks like an issue with TOML inheritance. Try this
wrangler.json instead:wrangler.json516B
HAlso note that for Service Bindings to work, you need to have a separate
wrangler devagent-loop WorkerBThanks! Now I am struggling with calling one workflow from another. Is this possible? Both workflows are folders in the same monorepo. Let's say I want to call RunSnapWorkflow from RunEpisodeWorkflow. The things I have trouble with:
Should i bind RunSnapWorkflow as a service and use fetch interface?
- When I add the workflow_b binding to workflow_a wrangler.toml, i get a deploy error: "Your Worker depends on the following Workflows, which are not exported in your entrypoint file: RunSnapWorkflow. You should export these objects from your entrypoint, src/index.ts."
- If i copy the RunSnapWorkflow class definition to RunEpisodeWorkflow, i can deploy. but when i call RunSnapWorkflow.create() "I get an error: Error: workflow.not_found "
Should i bind RunSnapWorkflow as a service and use fetch interface?
Bwhen i try to bind as a service and call via fetch, i get "workflow.not_found" error... Completely stumped here
MCloudflare Docs
This guide details the Workflows API within Cloudflare Workers, including methods, types, and usage examples.
MWithout your
wrangler.json files it is hard to guess at what you are doing though. There’s nothing special here: make sure you are exporting each Workflow, and have a binding to the ones you want to call via the Workers API.
Lcan I list locally run workflows?
pnpm wrangler workflows list doens't return anything as I am just testing in dev for now and want to run the local workflow runsLalso, is there something equivalent as Inngest's NonRetriableError? https://www.inngest.com/docs/features/inngest-functions/error-retries/inngest-errors#prevent-any-additional-retries
MCloudflare Docs
This guide details the Workflows API within Cloudflare Workers, including methods, types, and usage examples.
LOh nice thank you
LI'm getting this error with the cloudflare blank starter repo when I change the index.ts to use workflows (the test passed before0
Lcan someone help with this one please? not sure if it's an issue on my side or CF. it's just a log and everything else works fine but it seems a bit weird. it has something to do with workflows so should have posted it here I guess workers-and-pages-helpWeird "run" error with workers + CF workflows
JHey, I think I've got a bug. 
Every so often workflows will fail to find the toISOString method on the WorkflowEvent.
Which leads me to belive sometimes it's not parsing the event into a date object or losing that method somewhere.
Its failed 10 workflows for me overnight
Every so often workflows will fail to find the toISOString method on the WorkflowEvent.timestamp.toISOString is not a functionWhich leads me to belive sometimes it's not parsing the event into a date object or losing that method somewhere.
Its failed 10 workflows for me overnight
J@Skye yes sure 
export class ActionsWorkflow extends WorkflowEntrypoint<Env, StockTakeActionEvent> {
async run(event: WorkflowEvent<StockTakeActionEvent>, step: WorkflowStep) {
// some other code, but doesn't interact with event
const timestamp = event.timestamp.toISOString()
}
}
export class ActionsWorkflow extends WorkflowEntrypoint<Env, StockTakeActionEvent> {
async run(event: WorkflowEvent<StockTakeActionEvent>, step: WorkflowStep) {
// some other code, but doesn't interact with event
const timestamp = event.timestamp.toISOString()
}
}
KHi, folks, would there be a problem with using a for loop over a step.do & a step.sleep?
for example:
i'm not sure how this works behind the scenes, but i read that the step names need to be static so that they will be cached, so i imagine that if the workflow shuts down after the first sleep, it will reiterate over configs but "skip" the steps
for example:
i'm not sure how this works behind the scenes, but i read that the step names need to be static so that they will be cached, so i imagine that if the workflow shuts down after the first sleep, it will reiterate over configs but "skip" the steps
do 1 and sleep 1 and pick up from do 2. is that correct?