• Peter Aubrey
  • NEWBIE
  • 0 Points
  • Member since 2015

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 1
    Questions
  • 1
    Replies
Hello everyone,

Looking for some advice. We are encountering the dreaded ConcurrentPerOrgApex limit which I realise can be tricky to deal with. We've researched a number of articles including:
  • https://developer.salesforce.com/blogs/engineering/2013/05/force-com-concurrent-request-limits.html
  • http://www.slideshare.net/developerforce/concurrency-designpatterns-mt
  • http://www.eltoro.it/ArticleViewer?id=a07A000000NPRi8IAH
Salesforce support aren't being the most helpful and wanted to confirm a couple of things:
  1. Documentation states that its Apex, SOQL, etc. that counts towards this limit. We've used Developer Console to look at timelines and looking only at the Apex and DB requests, they are always coming back in a few miliseconds, no where near five seconds. All actvitities may take longer than 5 seconds. So should we be reading the timeline from the start to the end for all parts, or just the Apex and DB rows?
  2. We have Email-to-Case enabled and one Email-to-Apex handler. We've been told that everytime E2C processes an email, the E2A handler is also fired, even though emails are NOT sent to this address. Is this correct? Anyone else found this?
Any other hints and tips on how to track these down without spending 10% of our license fee to get the monitoring option would be greatly appreciated.
Hello everyone,

Looking for some advice. We are encountering the dreaded ConcurrentPerOrgApex limit which I realise can be tricky to deal with. We've researched a number of articles including:
  • https://developer.salesforce.com/blogs/engineering/2013/05/force-com-concurrent-request-limits.html
  • http://www.slideshare.net/developerforce/concurrency-designpatterns-mt
  • http://www.eltoro.it/ArticleViewer?id=a07A000000NPRi8IAH
Salesforce support aren't being the most helpful and wanted to confirm a couple of things:
  1. Documentation states that its Apex, SOQL, etc. that counts towards this limit. We've used Developer Console to look at timelines and looking only at the Apex and DB requests, they are always coming back in a few miliseconds, no where near five seconds. All actvitities may take longer than 5 seconds. So should we be reading the timeline from the start to the end for all parts, or just the Apex and DB rows?
  2. We have Email-to-Case enabled and one Email-to-Apex handler. We've been told that everytime E2C processes an email, the E2A handler is also fired, even though emails are NOT sent to this address. Is this correct? Anyone else found this?
Any other hints and tips on how to track these down without spending 10% of our license fee to get the monitoring option would be greatly appreciated.