All pipelineactivityin Codefreshcan be viewedin the*Builds* tab.

*The globalbuild view showsbuilds for allprojectsacross your organization

*The project-based view from the settings inside an individualprojectshows the builds for theselectedproject

Viewactivityfor Codefreshpipelines inin the**Builds** tab.

*Globalbuild view: The default view, displaysbuilds for allpipelines for all projectsacross your organization.

*Project build view: Selecting aprojectdisplays the builds for thepipelines in theproject.

Both views have the same controls and filters.

You can choose to restart any pipeline by clicking the button at the top right corner.

You can restart a failed pipeline either from the beginning or from a failed step.

* Restart from beginning

Restarts the pipeline with the**same** state as in its original execution, including the original Git commit.

* Restart from failed step

Restarts the pipeline from the step that failed in the previous execution. Similar to restarting from the beginning, restarting from a failed step also restarts the pipeline with the same state at that point in time, including the original Git commit. You can restart from the Builds page or directly from the specific step that failed.

**Restart pipeline from Builds view**

* In the row with the pipeline to restart, click**Restart**, and then select the required option.

{% include

image.html

lightbox="true"

file="/images/pipeline/monitoring/restart-pipeline.png"

url="/images/pipeline/monitoring/restart-pipeline.png"

alt="Restart a pipeline"

alt="Builds view:Restart a pipeline"

caption="Restart a pipeline"

max-width="70%"

%}

If the pipeline has failed, you can choose to restart it only from the failed step and onwards.

You can also restart from a failed step right from the graphical view:

**Restart from step view**

* Click the pipeline to view its steps.

* Go to the failed step, right-click and then select**Restart from this step**.

{% include

image.html

lightbox="true"

file="/images/pipeline/monitoring/restart-failed.png"

url="/images/pipeline/monitoring/restart-failed.png"

alt="Restart from a failed step"

caption="Restart from a failed step"

alt="Step view:Restart from failed step"

caption="Step view:Restart from failed step"

max-width="70%"

%}

If your pipeline has some flaky steps, you can also use the[retry syntax]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/#retrying-a-step) in your yaml instead of restarting them manually each time they fail.

max-width="50%"

%}

If you havesetupa[Git trigger]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/) in Codefresh then by default this happens automatically without any other configuration

for all automated commits(that are comingfrom webhooks).

If you haveset upa[Git trigger]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/) in Codefresh, then by default this happens automatically without any other configuration

for all automated commits from webhooks.

If you start a build manually then by default the git status will**not** be updated (i.e. the result of the pipeline

will not affect the status of Pull request)

- Builds in pending approval will**be** counted when determining the concurrency limit for a pipeline

- Honor the option defined globally in your Codefresh account

-**Restart pipeline**

**Permit restart pipeline from failed step**: When enabled (the default), allows users to restart the pipeline directly from the failed step. Otherwise, users can only restart the pipeline from the beginning.

As this option restarts the failed step with the same state, you may find it useful to disable this option based on the usage. For example, restarting a custom Helm promotion step that failed, restarts the step with the same revision and does not promote the newest images as it should.

By default, all clusters integrated with Codefresh are automatically available for all pipelines in the account.

The inject cluster option when enabled for the account allows you to selectively restrict the clusters which can be accessed from pipelines created for the user account.