Timeout in 2016 Stripping productions
A small percentage of 2016 Stripping production jobs failed due to some rare events taking order of 1 hour to process. In local tests for two of the input files where this happened, StrippingB2CCHBd2LcLcKPiLine
showed up as the line causing this.
The line doesn't seem to have a cap on the MaxCandidates
it creates, and perhaps the combinatorics spiral out of control in some busy events, causing it to stall for so long. The line authors are requested to troubleshoot this and fix the line for future usage. In the current campaign, the code won't be changed.