Deactivateservices leaves the stack (environment) in the active state

Using the API, when I POST deactivateservices on a stack, the services go inactive, but the the stack state remains “active”. In the UI the stack appears to be inactive with the yellow triangle, but if you look at the API view, the state is “active”

If this is “by design” let me know and I’ll work around it by just checking the status of all of the services. I guess in any case, I’ll have to work around it but this is a bug I’d like to know.

Stack state doesn’t directly reflect the services state. It’s currently a UI generated state.

We are planning on introducing healthstate field introduced for the stack. It’s currently closed as we have introduced it, but are working through the small bugs related to it.