Workers: add cron trigger changelog and docs for Python Workers. #21875
Conversation
dom96
requested review from
irvinebroque,
ToriLindsay,
a team,
jasnell,
mikenomitch,
GregBrimble and
WalshyDev
as code owners
github-actions
bot
assigned dcpena, haleycode, patriciasantaana, pedrosousa, GregBrimble, irvinebroque, mikenomitch, ToriLindsay and WalshyDev
|
Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment. We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally. PR Change SummaryAnnounced the support for cron triggers in Python Workers, enhancing the documentation and changelog accordingly.
Modified Files
Added Files
How can I customize these reviews?Check out the Hyperlint AI Reviewer docs for more information on how to customize the review. If you just want to ignore it on this PR, you can add the Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add |
dom96
force-pushed
the
dominik/python-scheduled-worker
branch
2 times, most recently
from
7e05207 to
18095d4
Compare
| @@ -27,7 +27,42 @@ Cron Triggers execute on UTC time. | |||
|
|
|||
| To respond to a Cron Trigger, you must add a [`"scheduled"` handler](/workers/runtime-apis/handlers/scheduled/) to your Worker. | |||
|
|
|||
| <Render file="cron-trigger-example" /> | |||
There was a problem hiding this comment.
I'm not sure what the repercussions of this change are but I seem to recall that we intentionally wanted to move away from inlined examples in the docs to allow testing them properly in case they suddenly break.
Maybe someone with more docs experience can chime in.
dom96
force-pushed
the
dominik/python-scheduled-worker
branch
2 times, most recently
from
f518bea to
36e2735
Compare
dom96
force-pushed
the
dominik/python-scheduled-worker
branch
from
36e2735 to
a300f2a
Compare
|
|
||
| You can now create Python Workers which are executed via a cron trigger. | ||
|
|
||
| This is similar to how it's done in JavaScript workers, simply define a scheduled event |
There was a problem hiding this comment.
Optional - you can link here to remind people of the JS API
src/content/changelog/workers/2025-04-22-python-worker-cron-triggers.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: ToriLindsay <[email protected]>
Summary
Cron triggers have been recently fixed in Python Workers so let's announce them in our docs and changelog.
Note that Python Workers need to be triggered differently when testing locally. The
/__scheduledendpoint doesn't work because it relies on wrangler injecting some JavaScript code which is not possible for Python Workers. I spoke with @penalosa about this and it seems the long-term plan is to move to the/cdn-cgi/handler/scheduledhandler eventually anyway, so we may as well point Python Workers devs to it.Documentation checklist