---
title: Workzone Global Settings (hooks and performance settings)
description: "[![](https://izymes.com/wp-content/uploads/2022/08/Screen-Shot-2022-08-10-at-11.15.58-am-1.png)](https://izymes.com/wp-content/uploads/2022/08/Screen-Shot-2022-08-10-at-11.15.58-am-1.png) ## Pull Requests A detailed breakdown of each pull request configuration can be found within the settings in fine text. **1. Notify author when pull request merge is conflicted.** **Default: OFF** Notify the pull request author by email when…"
url: "https://izymes.com/docs/workzone-global-settings-hooks-and-performance-settings/"
updated: "2023-12-14"
category: Feature Guide Workzone
---

# Workzone Global Settings (hooks and performance settings)

[![](https://izymes.com/wp-content/uploads/2022/08/Screen-Shot-2022-08-10-at-11.15.58-am-1.png)](https://izymes.com/wp-content/uploads/2022/08/Screen-Shot-2022-08-10-at-11.15.58-am-1.png)

## Pull Requests

A detailed breakdown of each pull request configuration can be found within the settings in fine text.

   **1. Notify author when pull request merge is conflicted.** **Default: OFF** Notify the pull request author by email when the pull request merge is conflicted after rescoping. Workzone checks the mergeability after the target or the source of a pull request has been changed. This happens when another pull request is merged to the same target branch or if a commit/push has been made to the source branch. Checking mergeablility can be quite expensive as all registered merge checks need to be performed, including the Workzone merge condition checks.

## Performance

     **2. Reviewer group size limit.** **Default: 20** Limit the number of users per reviewer-group that can be added when a Pull Request is created. When Workzone adds reviewers from a reviewer group it needs to limit the total number to avoid all members of potentially large AD groups are added to the same pull request. The recommendation is to create specific smaller groups such as ‘java-devs’ or ‘qa-ui’ etc and populate them with the target audience.     **3. Number of Groups per User Limit.** **Default: 99** When a reviewer approves a pull request and a group approval quota has been specified for a particular group Workzone needs to find out whether the user is a member of that group. In order to limit the search for the user’s group memberships a max limit is specified here. For instances with large AD where users can be a member of thousands of groups the value can be increased, however Workzone will take longer to identify reviewer group memberships. In some instances this limit was set to 8192 group memberships.           **4. Max Pull Request Age (Days).** **Default: unlimited** Limit the age of open pull requests considered for auto-merge on incoming build results. By default all open pull requests are considered. In large instances there can be many open pull requests. When a build result from a CI system is received, Workzone tries to match the commit hash with that of an open pull request in order to trigger a merge. If there are large amounts of open pull requests this search can take up too much time and the event queue overflows. When limiting the age of open pull requests, the search will finish earlier. And let’s be honest – who wants to merge a pull request that’s older than 90 days??        [Try Workzone!](https://marketplace.atlassian.com/apps/1211303/workzone-pullrequest-workflow?hosting=datacenter&tab=overview)