Warn about the importance of catching exceptions in DO alarm handlers#28090
Merged
elithrar merged 1 commit intocloudflare:productionfrom Feb 5, 2026
Merged
Conversation
a-robinson
requested review from
a team,
Oxyjun,
elithrar,
joshthoward,
lambrospetrou,
mikenomitch and
vy-ton
as code owners
github-actions
bot
added
product:durable-objects
github-actions
bot
assigned
elithrar,
joshthoward,
lambrospetrou,
mikenomitch,
Oxyjun and
vy-ton
Since otherwise a series of repeated uncaught exceptions can cause alarms to stop getting retried. That behavior was documented, but it isn't obvious that that means you may want to be careful about catching exceptions and scheduling your own new alarms.
a-robinson
force-pushed
the
a-robinson/alarm-exception-handling
branch
from
9cf0227 to
6f95bfb
Compare
lambrospetrou
approved these changes
Feb 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since otherwise a series of repeated uncaught exceptions can cause alarms to stop getting retried. That behavior was documented, but it isn't obvious that that means you may want to be careful about catching exceptions and scheduling your own new alarms.