flyctl machine clone is defunct?

For a machine app that I run, I’ve been trying to clone a vm without success for the past 2 days. I thought it might have been intermittent, since flyctl machine run has always worked for me. The err goes:

➜ fly m clone <vm-id> --config <toml> --name <machine-name> --region <r>            
Oops, something went wrong! Could you try that again?

The problem with run is, it doesn’t replicate env vars. I am not sure if clone does, but I’d prefer clone if it does (but it seems like clone and run are one and the same thing and that clone isn’t special in any way, shape, or form).

Is fly m clone going away? And never supposed to work?

cc: @eli clone still wouldn’t work… is this expected because the preview announcement mentioned it should?

May be it is reserved for the upcoming migrate-vm capability?

A nil pointer deref broke flyctl m clone: machines: clone breaks for non-postgres apps by ignoramous · Pull Request #1305 · superfly/flyctl · GitHub