Ah the container package is using alarms under the hood right now to keep your container alive, sinc
Ah the container package is using alarms under the hood right now to keep your container alive, since the DO has to be alive for the container to be alive. so probably that no-op alarm handler is overriding that and causing the thrashing
you can use
schedule on the container class instead of alarms for now if you need that functionality.

