How the get rid of "The deployment job is older than the previously succeeded deployment job" notifications?

I’ve setup notifications for failed pipelines. I have it in Slack and I have it via email. As I also have activated that older pipelines should be stopped when there is a newer one, GitLab triggers a “pipeline failure” notification for those pipelines even though this is a case that is explicitly allowed to happen.

Is there no way to make a difference between expected failures e.g., “The deployment job is older than the previously succeeded deployment job, and therefore cannot be run” and unexpected failures when it comes to notifications?

1 Like

Are you aware of settings/ci_cd#js-general-pipeline-settings where you can disable Skip outdated deployment jobs?

1 Like