After being "stopped" environments do not get re-activated

Something that I've observed so far in regards to present pipeline behaviour and environments:

upon the first deploy - environment gets created as expected and "stop" timer kicks in. However any subsequent deployments into the same environment do not trigger environment activation

resulting in "zombie" deployments.

Deployments are still being recorded against that environment etc. but auto_stop_in: seems to have no effect