You can see that only two steps were ignored. If you rerun the pipeline and approve

it, the other two steps will be ignored.

Codefresh has the ability to limit the amount of running builds for a specific pipeline with several concurrency policies in the pipeline settings. You can choose if a build that is in a pending approval state will count against the concurrency limits or not.

As an example let's say that the concurrency limit for a specific pipeline is set to 2. Currently there is one active/running build and a second build that is pending approval.

1. If the pipeline settings define that builds in pending approval**count** against concurrency, then if you launch a third build it will wait until one of the first two has finished

1. If the pipeline settings define that builds in pending approval**do not** count against concurrency, then if you launch a third build it will execute right away.

There isn't a correct or wrong way to set this option. It depends on your organization and if your consider builds pending approval as "active" or not.

You can either set this option[differently per pipeline]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#policies), or globally in your account at your[account settings](https://g.codefresh.io/account-admin/account-conf/pipeline-settings).

If you also enable[Slack integration]({{site.baseurl}}/docs/integrations/notifications/slack-integration/) in Codefresh you will have the choice of approving/rejecting a pipeline

- Keep the volume available

- Discard the volume

- Honor the option defined globally in your Codefresh account

-**Pending approval concurrency limit effect**: decide if a build that is pending approval[counts against]({{site.baseurl}}/docs/codefresh-yaml/steps/approval/#define-concurrency-limits) the concurrency limits or not

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

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

- Honor the option defined globally in your Codefresh account

The**Pipeline and Trigger Concurrency** limits are very important as they allow you to define how many instances of a pipeline can run in parallel when multiple commits or multiple pull requests take place.

- Concurrency behavior for pending builds -[documentation]({{site.baseurl}}/docs/codefresh-yaml/steps/approval/#define-concurrency-limits)

- Jira integration -[documentation]({{site.baseurl}}/docs/yaml-examples/examples/sending-the-notification-to-jira/)

- SLA details -[documentation]({{site.baseurl}}/docs/terms-and-privacy-policy/sla/)

- Hide inaccessible clusters in the Kubernetes dashboard -[documentation]({{site.baseurl}}/docs/deploy-to-kubernetes/manage-kubernetes/#accessing-the-kubernetes-dashboard)