You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fc3cbaa
Browse filesBrowse the repository at this point in the historyBrowse files
Support `workflow` entries in the `exports` configuration map
10
+
11
+
A Worker can now declare the Workflows it defines in `exports`, keyed by the `WorkflowEntrypoint` class name:
12
+
13
+
```jsonc
14
+
{
15
+
"exports": {
16
+
"MyWorkflow": {
17
+
"type":"workflow",
18
+
"name":"my-workflow",
19
+
"limits": { "steps":100 },
20
+
"schedules":"0 * * * *",
21
+
},
22
+
},
23
+
}
24
+
```
25
+
26
+
A `workflow` export accepts the same settings as a `workflows` binding: `limits`, `concurrency`, `schedules`, and `default_retention`. `wrangler deploy` and `wrangler versions upload` send these entries to the upload API by name, and `wrangler deploy` and `wrangler triggers deploy` provision the Workflow with its settings, just as they do for `workflows` bindings owned by the Worker. A Workflow may be declared both as a binding and as an export, as long as both declarations use the same class and do not set the same setting to different values. A binding to another Worker's Workflow cannot share a name with an export. `@cloudflare/config` adds the matching `exports.workflow()` helper. Local development does not yet act on these entries.
0 commit comments