If it’s not starting because of some CPU issue that why you don’t see issue there? Why should I do in this situation? I’m paying for the CPU that I can’t use? It’s ridiculous.
There’s no indication that CPU load was preventing your Machine from booting. Fwiw, that specific failed health check doesn’t mean the Machine isn’t running, but it can be an indicator that CPU could be impacting performance on that member. Basically, if the check is failing on your replica and you don’t have synchronous replication configured, replica isn’t falling out of sync, etc. it should be safe to ignore it.
If self-serve is causing you issues and think a managed solution would offer less headaches, I would consider checking out Supabase: