# Workflow doesn't work correctly when non-blocking job fails

**URL:** <https://discuss.circleci.com/t/workflow-doesnt-work-correctly-when-non-blocking-job-fails/35021>\
**Category:** Bug Reports\
**Created:** [March 17, 2020, 3:27pm UTC](https://discuss.circleci.com/t/workflow-doesnt-work-correctly-when-non-blocking-job-fails/35021 "2020-03-17T15:27:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![polson136](https://avatars.discourse-cdn.com/v4/letter/p/a88e57/32.png) [@polson136](https://discuss.circleci.com/u/polson136)\
**Post date:** [March 17, 2020, 3:27pm UTC](https://discuss.circleci.com/t/workflow-doesnt-work-correctly-when-non-blocking-job-fails/35021/1 "2020-03-17T15:27:49Z")

</div>

![image](https://global.discourse-cdn.com/circleci/original/3X/7/e/7edf00c82d3f34b91cba037ddc5d56a185f49a02.png)

In this workflow, we have audit as non-blocking because it has false-positives sometimes and we want the option to ignore it in case we have a high priority deployment. However, unlike what this shows, the prod-push job has run successfully (I can see it in the “jobs” panel.) This is a regression, as it definitely used to work. Unfortunately, we cannot trigger the “hold” steps because the UI doesn’t think it’s ready.