Hi!

I am using automatic deployment with LifeTime API, which is based on forge component, and also goes in line with examples (https://success.outsystems.com/Documentation/11/Reference/OutSystems_APIs/LifeTime_API_v2/LifeTime_API_Examples). The problem is, sometimes ago I started getting this error too often:  "There was an error calculating outdated apps for deployment with key '...': Invalid status change: trying to change Staging with id  '...' from 'Validating' to 'Calculating apps to redeploy'"...  This is returned by "get deployment" method (https://success.outsystems.com/Documentation/11/Reference/OutSystems_APIs/LifeTime_API_v2#operation--deployments--DeploymentKey---get). I have changed logic to do 2 attempts, hoping that this is flickering, but sometimes this doesn't help still.

Today I had 3 failing attempts in a row, and then I have noticed that for such deployment, after creation, the validation didn't start in LifeTime! So it is created, and "Validate" button is shown, but it is not being executed. After I did it manually - it was able to continue. So this looks like a reason for the errors I am getting.

But how can I actually ensure that validation starts? Usually, it starts automatically after creation, but what if it did not, can it be forced to start, and how can this be checked?

There is send command method, but it says that "allowed commands are “start”, “continue” and “abort”. " (https://success.outsystems.com/Documentation/11/Reference/OutSystems_APIs/LifeTime_API_v2#operation--deployments--DeploymentKey---Command---post).