C
Civic Parrotfish
The Harness Enterprise plan hard caps account-wide concurrent pipeline executions at 1,000. PayPal's account is configured at 950 Addingsustomer full load to the current Harness account would breach the 1,000 cap at peak, causing widespread queuing across the entire PayPal account — affecting all BUs, not just Braintree.
Customers pipeline design compounds the problem: one Jenkins pipeline per CI task (separate pipelines for linting, unit tests, integration tests) means a single code commit triggers multiple concurrent executions simultaneously. Even with consolidation, the structural demand will remain high. Braintree's target is 5,000 concurrent slots.
Two-part ask:
  1. Increase the account-level concurrent execution ceiling beyond the Enterprise hard cap of 1,000. PayPal requires a negotiated contractual limit of at least 5,000 to safely absorb
  2. Provide real-time concurrency headroom via an API or Datadog metric so DPE can monitor consumption and model future BU onboarding impact before queuing occurs.
URGENT — Aug 13, 2026 deadline. If unresolved, Braintree's migration creates a systemic queuing risk for all 12,000+ PayPal developers on the shared Harness account. Every minute of queuing at account capacity directly blocks developer commits across PayPal Core, Xoom, Venmo, and all BUs.