awml / platforms / cloudflare-workers
Cloudflare Workers with Cron Triggers
A Cloudflare Worker started by Cron Triggers or by a request, running the workflow's own code on Cloudflare's network. This describes a kind of platform, not anyone's account. Cloudflare, which runs the Worker, sees everything it handles, and the fit has no field for that. Checked against Cloudflare's documentation on 22 October 2026.
- Off for up to
- no time: it is always on
A hosted service that is always on. Cron Triggers run on UTC time, and a change to them can take up to 15 minutes to reach Cloudflare's network. https://developers.cloudflare.com/workers/configuration/cron-triggers/
- Runs steps as
- code
The Worker runs the workflow's own code. A scheduled run may last up to 15 minutes of wall time. https://developers.cloudflare.com/workers/configuration/cron-triggers/ https://developers.cloudflare.com/workers/platform/limits/#duration
- AI from
- none
No agent runs there: only the Worker's own code. https://developers.cloudflare.com/workers/configuration/cron-triggers/
- Can call
- any company
A Worker can fetch any host, so its code can call any model company's API with a key kept as a secret. Workers AI also runs open models on Cloudflare itself. https://developers.cloudflare.com/workers/runtime-apis/fetch/ https://developers.cloudflare.com/workers-ai/
- Holds
- nothing
A Worker has no file system to keep folders in. State the workflow makes lives in KV, D1 or R2, which needs no at in the workflow. https://developers.cloudflare.com/workers/platform/storage-options/