If the alarm is not triggered prior to the worker environment existing, the alarm will still exist on the next boot up of the environment. If the alarm has past it's expiration date, it will never trigger.
This is non-intuitive from a development perspective. The current work around I have is to create an end point that grabs the instance of the durable object and then removes the alarm.
If the alarm is not triggered prior to the worker environment existing, the alarm will still exist on the next boot up of the environment. If the alarm has past it's expiration date, it will never trigger.
This is non-intuitive from a development perspective. The current work around I have is to create an end point that grabs the instance of the durable object and then removes the alarm.
This is currently being discussed as it related to tests, but development should also be considered. https://github.com/cloudflare/workers-sdk/issues/5388