I'm using the trigger-pipeline pipe to tigger and monitor other pipelines. I'm currently on v4.0.5. I just saw a result where the trigger-pipeline returned success even though the pipeline it ran failed with a system error: ✔ Build number 798 for alertremote@develop finished with result ERROR. ✔ Pipe finished successfully. INFO: Attempt number 97: Build number 798 for alertremote is IN_PROGRESS, waiting for pipeline to finish... INFO: Attempt number 98: Getting build info. The json returned by that pipeline has this state info: "state": { "type": "pipeline_state_completed", "name": "COMPLETED", "result": { "type": "pipeline_state_completed_error", "name": "ERROR" } } I know I'm using an older version of the pipe, but I checked the latest version of the trigger-pipeline code in the repo and it doesn't appear this case is accounted for in the latest version either. Can this be fixed?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

trigger-pipeline pipe results in success when pipeline fails with system error

Jay Seletz_tdgw99

I'm using the trigger-pipeline pipe to tigger and monitor other pipelines. I'm currently on v4.0.5.

I just saw a result where the trigger-pipeline returned success even though the pipeline it ran failed with a system error:

<span>INFO: Attempt number 98: Getting build info.<br></span><span>&#10004; Build number 798 for alertremote@develop finished with result ERROR.<br></span><span>&#10004; Pipe finished successfully.</span><span>INFO: Attempt number 97: Build number 798 for alertremote is IN_PROGRESS, waiting for pipeline to finish...<br></span>

The json returned by that pipeline has this state info:

"state": {
  "type": "pipeline_state_completed", 
  "name": "COMPLETED", 
  "result": {
    "type": "pipeline_state_completed_error", 
    "name": "ERROR"
  }
}

I know I'm using an older version of the pipe, but I checked the latest version of the trigger-pipeline code in the repo and it doesn't appear this case is accounted for in the latest version either. Can this be fixed?