function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Andrew Moore 24Andrew Moore 24 

Effects of SObject Collections (REST API) on ConcurrentPerOrgLongTxn REQUEST_LIMIT_EXCEEDED

Hello,

Recently, we have experienced several occurrences of REQUEST_LIMIT_EXEEDED - ConcurrentPerOrgLongTxn Limit exceeded.  We have multiple integrations using API's into Salesforce, as well as a large SF user base.  I'm struggling to understand how we can determine what the underlying cause is.  It would be helpful to know what transactions / requests are running long at the time of this error to narrow down our investigation.  According to SF, this error can occur when 10 concurrent requests are running, lasting more than 5 seconds each.

https://salesforce.stackexchange.com/questions/149335/first-error-unknown-exception-concurrentperorglongtxn-limit-exceeded

Along with this, I am curious what affect the Composite SObject Collections feature introduced in v42.0 would have on this.

https://developer.salesforce.com/docs/atlas.en-us.212.0.api_rest.meta/api_rest/resources_composite_sobjects_collections.htm

If we assume a single update on an object takes 1 second, and we use the composite SObject Collection feature to update 200 objects, is this considered 200 1-second transactions which will have no effect on the ConcurrentPerOrgLongTxn Limit, or is it considered 1 200-second transaction, which WOULD have an effect on the ConcurrentPerOrgLongTxn Limit.

Thanks,

Andrew Moore
 
Admin SVD Admin SVDAdmin SVD Admin SVD

I don't have an answer for your question, but....

I have onter question related to this.

Are you able to update objects using SObject Collection feature referencing those objects with external Ids?

thanks!