Today it is possible to provide failure messaging - and disable an automation if there is a failure (such as the stored token for an external service belongs to a user who doesn’t have access to the system any longer).
enhance this capability to include the ability to return messaging on success (changed project state to xyz), and for in progress allow us to return the 2000 severity (which exists) and display that message for “in progress” states.
For the in progress it would be something like “too many requests, waiting to try again” or “external service is not responding”. This way we can communicate to the end user why it is “in progress” still. Right now they go “its stuck in progress it must not be working!” and trigger something again… and again. If its the too many requests situation, then they are just making it worse.
The in progress messaging is needed for any asynchronous solution as well.