Close popover
Armin Schmid (schma)
Lead System Architect - Pega Consulting
Pegasystems Inc.
schma Member since 2013 6 posts
Posted: July 30, 2020
Last activity: December 29, 2020

When is a branch too big?

In our current project, we're using branches and Deployment Manager to merge and deploy branches. We ran into a problem when we tried to merge one specific branch. Other branches didn't have that and were merged smoothly and without any issues.

The logs showed a Timeout issue when calling certain pipeline services. As far as we can say, the corresponding Connector rule has a timeout of 30 seconds which can't be changed or controled through DSS or suchlike. This oob Connector rule is a final rule.

Our branch was quite big in terms of number of rules: more than 350 rules. Apparently too big! Too many rules for this service to come back with a response within the timeout.

We moved 100 rules to a second branch. Now we were able to merge both branches.

I agree that this branch had a quite unusual number of rules. And I agree that we should prefer small and specific branches. On the other hand, sometimes it makes sense to put quite a number of field values, icons or other rules into one big branch.

So I'm wondering why we cannot configure the timeout. Has anybody else already had the same issue? What do you think?

***Edited by Moderator: Pallavi to change content type from Discussion to Question***

Pega Platform 8.4 DevOps Senior System Architect