# Promotion UI silently fails if no pipeline can be triggered

**URL:** <https://drone.discourse.group/t/promotion-ui-silently-fails-if-no-pipeline-can-be-triggered/11114>\
**Category:** Drone Bugs\
**Created:** [February 7, 2021, 1:29pm UTC](https://drone.discourse.group/t/promotion-ui-silently-fails-if-no-pipeline-can-be-triggered/11114 "2021-02-07T13:29:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ashwilliams1](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/ashwilliams1/32/5549_2.png) [@ashwilliams1](https://drone.discourse.group/u/ashwilliams1)\
**Post date:** [February 7, 2021, 9:24pm UTC](https://drone.discourse.group/t/promotion-ui-silently-fails-if-no-pipeline-can-be-triggered/11114/2 "2021-02-07T21:24:13Z")

</div>

> [@Troubleshooting performance issues in build](https://drone.discourse.group/t/troubleshooting-performance-issues-in-build/8716/1):
>
> There is a JS error, so I guess the information on pipelines I could trigger must be in the frontend somewhere. If so, the promotion button should not be active if no promotion can be triggered.

not quite … it is the backend, specifically your yaml configuration file that is dynamically fetched and evaluated, that determines whether or not a pipeline can be triggered. If you have a trigger section in your yaml that evaluates to false, and no pipeline executes, a `null` object is returned to the user interface, hence the stacktrace.

but yes, we should do a better job of handling the null and surfacing why no pipeline executes.

---

_[View the full topic](https://drone.discourse.group/t/promotion-ui-silently-fails-if-no-pipeline-can-be-triggered/11114)._
