To get the general problem, please see the epic description.
TL;DR: In some situations, the deployment of an application can be delayed within marathon (e.g. failing service and not enough resources). Currently, we show it as recovering or deploying although marathon might not be trying to deploy it anymore due to its delayed state.
We need to think about where the action to reset the delayed state should be shown