I suspect this is a regression: resources in a dirty state are not returned by the APIs, which prevents the client from showing and managing them according to their current state.
In general, hiding resources in a dirty state makes them disappear from any catalogue listing, which is confusing at the very least.

For example, when a resource is cloned, it's marked as dirty to prevent changes to the resource until the clone operation is completed. If the operation takes longer, the user will see the original resources disappear, while the cloned resource is not created yet.
We want instead to return the resource, along with the "executions" info, so that the client can apply the expected labels and constraints, and provide users the expected feedback.