Jun 12, 2023 · Jun 7, 2023 · Jun 7, 2023 · Jun 7, 2023 · Jun 11, 2023 · Jun 11, 2023
diff --git a/_docs/pipelines/monitoring-pipelines.md b/_docs/pipelines/monitoring-pipelines.md
 * Global build view: The default view, displays builds for all pipelines for all projects across your organization.
 * Project build view: Selecting a project displays the builds for the pipelines in the project.

 As a user, you can see builds from all pipelines you have access to. If your permissions do not include access to specific pipelines, you will not see builds from those pipelines.
 As a user, you can see builds from all pipelines you have access to. If your permissions do not include access to specific pipelines, you will not see builds from those pipelines.

 ## Viewing pipeline status

 Each screen contains all builds sorted from the most recent to the oldest. The first time you visit
 the screen there are no filters defined. To narrow the list, use the filters on the top
 of the screen.
 The Builds page for a pipeline displays by default all builds sorted from the most recent to the oldest. To narrow the list, you can use the date range filter, and additional filters at the top of the page.

 {% include
 image.html
 max-width="80%"
 %}

 ## Viewing status for pipeline builds

 Each build's status is displayed beneath the build details, identifiable by a distinct icon. Refer to the table below for a description of the various statuses associated with pipeline builds.

 ### Applying filters on the build view

 Directly above the list you can find several filters.
 {: .table .table-bordered .table-hover}
 | Pipeline Build Status Icon &nbsp; &nbsp; &nbsp;   | Description   |
 | ------------------------| ---------------- |
 |{::nomarkdown}<img src="../../../images/icons/pipeline-build-running.png" display=inline-block/> {:/}| Pipeline build is currently running. |
 |{::nomarkdown}<img src="../../../images/icons/pipeline-build-successful.png" display=inline-block/> {:/}| Pipeline build completed successfully.  |
 |{::nomarkdown}<img src="../../../images/icons/pipeline-build-delayed.png" display=inline-block/> {:/}| Pipeline build run has been delayed as there are no free builders. <br>A build can be delayed for a maximum of seven days. Each account can have up to a 1000 delayed builds at any time. <br>{::nomarkdown}<b>NOTE</b>: <ul><li>Builds that are delayed for more than seven days are terminated with a _Delay time limit exceeded_ reason. </li><li>If the total number of delayed builds for an account exceed 1000, older builds are terminated with a <i>Maximum delayed workflows exceeded</i> reason.</li></ul>{:/}|
 |{::nomarkdown}<img src="../../../images/icons/pipeline-build-pending-approval.png" display=inline-block/> {:/}| Pipeline build is pending approval. |
 |{::nomarkdown}<img src="../../../images/icons/pipeline-build-denied.png" display=inline-block/> {:/}| Pipeline build pending approval has been denied approval. |
 |{::nomarkdown}<img src="../../../images/icons/pipeline-build-terminating.png" display=inline-block/> {:/}| Pipeline build is gracefully terminating execution.|
 |{::nomarkdown}<img src="../../../images/icons/pipeline-build-terminated.png" display=inline-block/> {:/}| Pipeline build execution has been manually or automatically terminated. |
 |{::nomarkdown}<img src="../../../images/icons/pipeline-build-failed-error.png" display=inline-block/> {:/}| Pipeline build execution has failed because of errors. |


 ### Applying filters on the build view

 At the most basic level youcan choose between
 The **Add Filters** option allows youto filter the list of builds by additional criteria, including build status.

 * *Running* builds that are currently executing
 * *Pending* builds which are queued and waiting to start
 * *Delayed* builds which cannot run yet, because there are no free pipeline builders.
   A build can be delayed for a maximum of seven days, and each account can have up to 1000 delayed builds at any time.
    * Builds that are delayed for more than seven days are terminated with a _Delay time limit exceeded_ reason.
    * If the total number of delayed builds exceed 1000, older builds are terminated with a _Maximum delayed workflows exceeded_ reason.
 At the most basic level, you can filter by status, choosing between Running/Pending/Delayed builds.

 * *All* builds regardless of running stage (this is the default)

 You can further filter the builds by choosing the various filter types that specify the build job.



 Notice that all filters are multiple-choice so you can select multiple values for each filter category.
 At any given point you can see all the active filtersontop of the screen.
 At any given point you can see all the active filtersat thetop of the page the screen.

 {% include
 image.html



 ### Reviewing theyaml for the pipeline
 ### Reviewing theYAML for the pipeline

 From the step details you can also click on the yaml tab to see the yaml segment for that individual step:

diff --git a/images/icons/pipeline-build-delayed.png b/images/icons/pipeline-build-delayed.png
diff --git a/images/icons/pipeline-build-denied.png b/images/icons/pipeline-build-denied.png
diff --git a/images/icons/pipeline-build-failed-error.png b/images/icons/pipeline-build-failed-error.png
diff --git a/images/icons/pipeline-build-pending-approval.png b/images/icons/pipeline-build-pending-approval.png
diff --git a/images/icons/pipeline-build-running.png b/images/icons/pipeline-build-running.png
diff --git a/images/icons/pipeline-build-successful.png b/images/icons/pipeline-build-successful.png
diff --git a/images/icons/pipeline-build-terminated.png b/images/icons/pipeline-build-terminated.png
diff --git a/images/icons/pipeline-build-terminating.png b/images/icons/pipeline-build-terminating.png
Original file line number	Diff line number	Diff line change
Expand Up		@@ -12,13 +12,9 @@ View activity for Codefresh pipelines in in the Builds tab.
		* Global build view: The default view, displays builds for all pipelines for all projects across your organization.
		* Project build view: Selecting a project displays the builds for the pipelines in the project.

		As a user, you can see builds from all pipelines you have access to. If your permissions do not include access to specific pipelines, you will not see builds from those pipelines.
		As a user, you can see builds from all pipelines you have access to. If your permissions do not include access to specific pipelines, you will not see builds from those pipelines.

		## Viewing pipeline status

		Each screen contains all builds sorted from the most recent to the oldest. The first time you visit
		the screen there are no filters defined. To narrow the list, use the filters on the top
		of the screen.
		The Builds page for a pipeline displays by default all builds sorted from the most recent to the oldest. To narrow the list, you can use the date range filter, and additional filters at the top of the page.

		{% include
		image.html
Expand All		@@ -30,22 +26,30 @@ caption="Pipeline activity"
		max-width="80%"
		%}

		## Viewing status for pipeline builds

		Each build's status is displayed beneath the build details, identifiable by a distinct icon. Refer to the table below for a description of the various statuses associated with pipeline builds.

		### Applying filters on the build view

		Directly above the list you can find several filters.
		{: .table .table-bordered .table-hover}
		\| Pipeline Build Status Icon       \| Description \|
		\| ------------------------\| ---------------- \|
		\|{::nomarkdown}<img src="../../../images/icons/pipeline-build-running.png" display=inline-block/> {:/}\| Pipeline build is currently running. \|
		\|{::nomarkdown}<img src="../../../images/icons/pipeline-build-successful.png" display=inline-block/> {:/}\| Pipeline build completed successfully. \|
		\|{::nomarkdown}<img src="../../../images/icons/pipeline-build-delayed.png" display=inline-block/> {:/}\| Pipeline build run has been delayed as there are no free builders. <br>A build can be delayed for a maximum of seven days. Each account can have up to a 1000 delayed builds at any time. <br>{::nomarkdown}<b>NOTE</b>: <ul><li>Builds that are delayed for more than seven days are terminated with a _Delay time limit exceeded_ reason. </li><li>If the total number of delayed builds for an account exceed 1000, older builds are terminated with a <i>Maximum delayed workflows exceeded</i> reason.</li></ul>{:/}\|
		\|{::nomarkdown}<img src="../../../images/icons/pipeline-build-pending-approval.png" display=inline-block/> {:/}\| Pipeline build is pending approval. \|
		\|{::nomarkdown}<img src="../../../images/icons/pipeline-build-denied.png" display=inline-block/> {:/}\| Pipeline build pending approval has been denied approval. \|
		\|{::nomarkdown}<img src="../../../images/icons/pipeline-build-terminating.png" display=inline-block/> {:/}\| Pipeline build is gracefully terminating execution.\|
		\|{::nomarkdown}<img src="../../../images/icons/pipeline-build-terminated.png" display=inline-block/> {:/}\| Pipeline build execution has been manually or automatically terminated. \|
		\|{::nomarkdown}<img src="../../../images/icons/pipeline-build-failed-error.png" display=inline-block/> {:/}\| Pipeline build execution has failed because of errors. \|


		### Applying filters on the build view

		At the most basic level youcan choose between
		The Add Filters option allows youto filter the list of builds by additional criteria, including build status.

		* Running builds that are currently executing
		* Pending builds which are queued and waiting to start
		* Delayed builds which cannot run yet, because there are no free pipeline builders.
		A build can be delayed for a maximum of seven days, and each account can have up to 1000 delayed builds at any time.
		* Builds that are delayed for more than seven days are terminated with a _Delay time limit exceeded_ reason.
		* If the total number of delayed builds exceed 1000, older builds are terminated with a _Maximum delayed workflows exceeded_ reason.
		At the most basic level, you can filter by status, choosing between Running/Pending/Delayed builds.

		* All builds regardless of running stage (this is the default)

		You can further filter the builds by choosing the various filter types that specify the build job.

Expand DownExpand Up		@@ -77,7 +81,7 @@ The available filters are:


		Notice that all filters are multiple-choice so you can select multiple values for each filter category.
		At any given point you can see all the active filtersontop of the screen.
		At any given point you can see all the active filtersat thetop of the page the screen.

		{% include
		image.html
Expand DownExpand Up		@@ -286,7 +290,7 @@ A variable with a strikethrough indicates an override by the same variable in a



		### Reviewing theyaml for the pipeline
		### Reviewing theYAML for the pipeline

		From the step details you can also click on the yaml tab to see the yaml segment for that individual step:

Expand Down