# Trigger by status unexpected behaviour

**URL:** <https://drone.discourse.group/t/trigger-by-status-unexpected-behaviour/9929>\
**Category:** Drone Support\
**Created:** [January 11, 2019, 11:49am UTC](https://drone.discourse.group/t/trigger-by-status-unexpected-behaviour/9929 "2019-01-11T11:49:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lukatera](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/lukatera/32/6051_2.png) [@lukatera](https://drone.discourse.group/u/lukatera)\
**Post date:** [January 11, 2019, 11:49am UTC](https://drone.discourse.group/t/trigger-by-status-unexpected-behaviour/9929/1 "2019-01-11T11:49:41Z")

</div>

I have this kind of pipeline definition:

```auto
trigger:
  status: [success, failure]

depends_on:
  - default

```

In case the default pipeline fails, the status of the second pipeline will be successful, i.e., all `*_STATUS` environment variables will report successful.This is unexpected behaviour. The pipeline as a whole is still marked as failed in UI. So essentially, there’s no way to detect failure in dependent pipelines which could be used to notify overall status of the pipeline. There’s an example in official docs explaining the exact use case: [https://docs.drone.io/config/pipeline/multi-machine/#triggers](https://docs.drone.io/config/pipeline/multi-machine/#triggers)

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [January 11, 2019, 10:39pm UTC](https://drone.discourse.group/t/trigger-by-status-unexpected-behaviour/9929/2 "2019-01-11T22:39:08Z")

</div>

There is an open issue for this in the core Drone repository issue tracker that can be subscribed to.

---

<div class="post-metadata">

**Author:** ![lukatera](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/lukatera/32/6051_2.png) [@lukatera](https://drone.discourse.group/u/lukatera)\
**Post date:** [January 14, 2019, 8:55am UTC](https://drone.discourse.group/t/trigger-by-status-unexpected-behaviour/9929/3 "2019-01-14T08:55:12Z")

</div>

I can not seem to find it in drone/drone. There’s only handful of issues that relate to Drone 1.0.  
This is the closest I could find, but it doesn’t seem to describe the problem above: [https://github.com/drone/drone/issues/2452](https://github.com/drone/drone/issues/2452)

---

<div class="post-metadata">

**Author:** ![lukatera](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/lukatera/32/6051_2.png) [@lukatera](https://drone.discourse.group/u/lukatera)\
**Post date:** [January 25, 2019, 12:18pm UTC](https://drone.discourse.group/t/trigger-by-status-unexpected-behaviour/9929/4 "2019-01-25T12:18:56Z")

</div>

@bradrydzewski Is this planned for 1.0 release? I still can’t find any mention of this issue and this affects 1.0-rc.5 as well.

---

<div class="post-metadata">

**Author:** ![bradrydzewski](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bradrydzewski/32/3513_2.png) [@bradrydzewski](https://drone.discourse.group/u/bradrydzewski)\
**Post date:** [January 25, 2019, 3:38pm UTC](https://drone.discourse.group/t/trigger-by-status-unexpected-behaviour/9929/5 "2019-01-25T15:38:55Z")

</div>

the existing issue is here: [https://github.com/drone/drone/issues/2553](https://github.com/drone/drone/issues/2553)

I will point out that this behavior _is working as designed_. The status is local to the currently running pipeline. I agree that this behavior is not intuitive, but it is not considered a bug. We may introduce a second global status variable prior to 1.0-final, so that you can differentiate between the status of the currently running pipeline vs the overall build.
