fix: handle invalid cron expressions in alarm handler

[HueCodes]

parseCronExpression throws for malformed cron strings. In the alarm
handler this prevents remaining schedules from executing and leaves
the invalid schedule in the database, blocking future alarms.

Wrap in try/catch and remove invalid schedules to unblock the loop.

[changeset-bot]

🦋 Changeset detected

Latest commit: 6b2d554

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
agents	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[threepointone]

we should probably validate them when adding

[HueCodes]

Yeah, getNextCronTime at line 1108 already throws for invalid expressions on creation. This just handles the edge case of corrupted data. Happy to add explicit validation there too if you'd prefer. Just let me know and thanks for the quick response!

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/cloudflare/agents@779

commit: 6b2d554

[threepointone]

can you explain to me how there would be corrupt data if we were always validating the input?

[HueCodes]

Good point. I was focused on catching edge cases at read-time, but validation at input makes more sense as the primary defense. I’ll update the PR after work. Still learning so thanks for your input.

[HueCodes]

Updated to validate cron expressions at input in schedule()