Concurrent apex limit exceeded in organizations with large amounts of process builder flows
Last updated 2020-10-21 ·Reference W-3616613 ·Reported By 114 users
Some organizations are seeing sporadic recurrence of concurrent apex issues in their organizations even without
- long running callouts,
- long running apex,
- long running queries.
These organizations have large amounts of process builder flows.
This behavior is being caused by long reload times of the process builder flows into an internal cache. While this is happening the apex jobs are becoming 'long running' which trips the organizations concurrent apex limit, and causes all further apex to fail until the long running jobs complete (after the flows are loaded into cache).
Heavy use of an organization with large amounts of process builder flows
None at this time
Reported By (114)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.