Hi… Yes, that sounds a lot like these two other threads the past couple days:
https://community.fly.io/t/machine-stuck-in-replaced-state/26648
https://community.fly.io/t/unkillable-zombie-machine-blocking-deployment/26661
My understanding is that the replaced state shouldn’t really ever be returned from fly m list (if that’s where you’re seeing it), only from a versioned query to the Machines API.
It’s being investigated last I heard…