https://blog.cloudflare.com/durable-objects-alarms/ > Under the hood, Alarms are implemented by mak
https://blog.cloudflare.com/durable-objects-alarms/
The DO alarm's blog post references the storage blog post:
https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/#part-2-output-gates
From what I understand of this blog post, the following would be how things would play out? Which doesn't seem to align with <any failure within the alarm handler causes all alarm calls in that call to be ignored and for the original to be retried>
Under the hood, Alarms are implemented by making reads and writes to the storage layer. This means Alarmandgetoperations follow the same rules as any other storage operationset
The DO alarm's blog post references the storage blog post:
https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/#part-2-output-gates
From what I understand of this blog post, the following would be how things would play out? Which doesn't seem to align with <any failure within the alarm handler causes all alarm calls in that call to be ignored and for the original to be retried>

