Forum Discussion
1 Reply
- MatthiasNew Contributor III
you’ll usually see this in sub-pipelines, which were triggered by another pipeline - where the parent pipeline has been stopped or failed.
it’s usually not tied to the pipeline you see this error - nor to the snaps it belongs to - they were simply aborted.