So like you thought, these jobs from your release_command were hanging around (as they were waiting for a confirmation that would never come). They were still emitting logs, so that’s why you were seeing them in fly-metrics.
Is there a way to cancel the startup of those versions? The app is now working fine, but the failed attempts of previous deployments are flooding the logs.
There isn’t a way to cancel release_command jobs.That said, we’ve just now merged a PR to fix this-- once it rolls out, release jobs won’t hang around indefinitely anymore.
We manually killed your old release jobs, and you should see them go away in the logs within an hour 