Deployment stuck on 'Scheduled'
There are some situations where you may see your deployment is stuck as ‘Scheduled’. Below you will find a description of what is happening in each situation and how you can fix it.
- Part of the deployment record is greyed out and the Deploy button cannot be clicked.
The problem in this situation could be one of the below:
The deployment has been created without a value in the To Org field. The user that has created the deployment doesn’t have access to the org credentials linked to the environment that should have been selected in this field.
The deployment has been created without any deployment steps. This could be due to any of the following reasons:
- The user story doesn't have any components in the User Story Selections section because nothing was committed, the commit returned a No Changes status or the commit failed. You should have received an email explaining why the commit failed.
- The promotion process (merge of the feature branches into the promotion branch) that creates the deployment failed, and the Git Promotion step was not created. You should have received an email explaining why the promotion process failed.
- The deployment screen looks fine, but the deployment status is ‘Scheduled’.
This could be due to one of these reasons:
You have clicked on Deploy and have selected Deploy Later instead of Deploy Now.
The deployment was manually created from the promotion. In this case, you will have to start the deployment manually. It won’t start automatically.