Skip to content

Commit 1072186

Browse files
committed
cron triggers
1 parent a21c2a0 commit 1072186

File tree

2 files changed

+12
-3
lines changed

2 files changed

+12
-3
lines changed

src/content/docs/workers/configuration/cron-triggers.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,12 @@ Cron Triggers allow users to map a cron expression to a Worker using a [`schedul
1111

1212
Cron Triggers are ideal for running periodic jobs, such as for maintenance or calling third-party APIs to collect up-to-date data. Workers scheduled by Cron Triggers will run on underutilized machines to make the best use of Cloudflare's capacity and route traffic efficiently.
1313

14+
:::note
15+
16+
Cron Triggers can also be combined with [Workflows](/workflows/) to trigger multi-step, long-running tasks. You can [bind to a Workflow](/workflows/build/workers-api/) from directly from your Cron Trigger to execute a Workflow on a schedule.
17+
18+
:::
19+
1420
Cron Triggers execute on UTC time.
1521

1622
## Add a Cron Trigger

src/content/docs/workflows/build/workers-api.mdx

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,9 @@ sidebar:
88

99
TODO
1010

11+
## Binding
12+
13+
TODO
1114

1215
## Interacting with Workflows
1316

@@ -40,14 +43,14 @@ TODO - into to steps
4043
* <code>step.do(name: string, callback: (): RpcSerializable, config?: StepConfig): Promise&lt;T&gt;</code>
4144

4245
* TODO - describe each param
43-
* TODO -
46+
* TODO -
4447

4548
TODO - show an example
4649
TODO - show an example of dynamically creating a step
4750

4851
* <code>step.sleep(name: string, duration: WorkflowDuration): Promise&lt;void&gt;</code>
4952

50-
* TODO -
53+
* TODO -
5154

5255
TODO - show an example
5356

@@ -56,4 +59,4 @@ TODO - show an example
5659

5760
TODO
5861

59-
## NonRetriableError
62+
## NonRetriableError

0 commit comments

Comments
 (0)