Copado Notification warning not completed.

When working with Copado, in order to avoid conflicts when many users attempt to commit or promote to the same branch at the same time warning messages are displayed to the users when they try to carry out an action on a branch at the same time than other users.

The pages where this background validation is being done in order to inform you about the potential conflict situation and let you decide what to do, are the following:

- Git Snapshot: when creating a snapshot of a branch which is currently being updated.
- Git Commit: when you click on this button within the user story page and you are trying to commit to a branch
- Branch Management: for all branches where potential conflict actions are being now running.
- User Story: if the next promotable branch is now being updated.
- Promotion: if the next promotable branch is now being updated.
- Deployment: the warning message will be displayed if the next promotable branch is now being updated.

A notification record will be created for every job that creates a warning. This means that, if a deployment is triggered 3 times, a notification record will be created every time since the 3 deployments will be processed on 3 different jobs.

Let's suppose that a deployment is triggered creating a notification record. The deployment fails unexpectedly and you trigger the deployment again. This would have created 2 notifications records. If the first notification record was not updated properly due to the unexpected failure of the deployment, the fact that the deployment is completed on the second try will not update the 1st notification since they are related to 2 different jobs. This will leave a Copado Notification "in progress" that has to be cancelled or completed manually. 

What could cause a Copado Notification not to be updated properly? 

1. Any job that fails unexpectedly might cause the Copado Notification not to be updated. Heroku issues, network connection issues or an unexpected response from Salesforce might cause this. 
2. A job might be also cancelled by our backend team after being stuck in progress for too long. In this case the Copado Notification will not be updated. 

We do our best to update these notifications no matter what happen with the job but there are still unexpected scenarios that may the notification not being updated.

How can you mark as complete a Copado Notification?

Whenever this happen, you can click on the Task Name to open the Copado Notification record.
User-added image

Navigate to the ParentId record to check if the task was actually completed or if it's still in progress. If it was already completed, you can update the notification manually enabling the Finished checkbox. 
User-added image

How did we do?