When-Pipeline-Fails.md

+You can find the state of any CI pipeline in the CI/CD entry of the project page.  When you click that, you'll see a list of all pipelines and their statuses:
+
+> ![image](uploads/6d3a20aaa004b5b4913a98b25f1af8ff/image.png  )
+
+If yours has failed, here are some things you can do to figure out what went wrong:
+
+1. Clicking on the "failed" icon will give you a page that looks like this:
+
+> ![image](uploads/413188e165828babde2ebaedf715312b/image.png  )
+
+2. From there, what you do depends on how it failed:
+
+2.1  If you think that one of the tests has failed, click on the Tests tab
+
+> ![image](uploads/bfe9deede4177b05e303a713b06da995/image.png )
+
+If tests have failed, clicking on "run_pipeline" will give you details about exactly what has failed and why.
+
+2.2  If you aren't sure what went wrong, click on the "failed" icon under Status.  That will show you a complete log of everything that happened.  In addition, on the right hand side of the screen, you'll see "Job Artifacts."  From there, you can browse and see all of the Logger output the various tests generated. If you need to add temporary debug output (because the pipeline doesn't fail on your machine, but it does fail in CI), you can use the LoggerManager to create the output and you'll find it in those artifacts.