Skip to content

Commit 75c70fc

Browse files
committed
[Workflows] Address scheduled Workflow review comments
1 parent fe3f676 commit 75c70fc

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

src/content/changelog/workflows/2026-05-13-cron-workflows.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Add cron schedules to a Workflow binding in wrangler.jsonc to creat
44
products:
55
- workflows
66
- workers
7-
date: 2026-05-13 12:00:00 UTC
7+
date: 2026-05-13
88
---
99

1010
You can now attach cron schedules directly to a Workflow binding in `wrangler.jsonc`. Each scheduled run creates a new Workflow instance automatically, so you do not need to define a separate Worker with a `scheduled` handler just to trigger your Workflow on an interval.

src/content/docs/workflows/build/trigger-workflows.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,7 @@ let instance = await env.MY_WORKFLOW.get("abc-123");
181181
await instance.resume(); // Returns Promise<void>
182182
```
183183

184-
Calling `resume` on an instance that is already running will throw an error.
184+
Calling `resume` on an instance that is not currently paused will have no effect.
185185

186186
:::caution
187187
If you have reached the maximum concurrent instances for your Workflow, resuming an instance may not restart it immediately. The instance will be queued until a concurrency slot becomes available.

0 commit comments

Comments
 (0)