Update Wrangler config Cron Triggers to match expected behaviour

[petebacondarwin]

Summary

If the user provides an empty array in their Wrangler configuration for Cron Triggers then Wrangler will remove all deployed triggers rather than leaving them untouched.

Blocked on cloudflare/workers-sdk#9266

Documentation checklist

• The documentation style guide has been adhered to.

[hyperlint-ai]

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 Summary

Updated Cron Triggers behavior in Wrangler configuration to ensure that an empty array removes all deployed triggers, while undefined properties leave existing triggers intact.

• Modified documentation to clarify that an empty crons array removes all Cron Triggers.
• Specified that triggers or crons being undefined retains current Cron Triggers.
• Updated examples to reflect the new behavior of Cron Triggers management.

Modified Files

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

---

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 hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

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 hyperlint-ignore to the PR to ignore the link check for this PR.