Answering the What & Why of Governor Limits in Salesforce

Answering the What & Why of Governor L i m i t s i n Salesforce

Rules e x i s t w h e r e v e r t h e r e a r e f i n i t e resources & S a l e s f o r c e i s n ’ t a n e x c e p t i o n . I n f a c t , S a l e s f o r c e G o v e r n o r l i m i t s a r e one o f t h e i m p o r t a n t s e t o f r e g u l a t i o n s t h a t has a l l o w e d i t t o s t a y as t h e w o r l d ’ s # 1 c u s t o m e r r e l a t i o n s h i p m a n a g e m e n t (CRM) p l a t f o r m .

These r u l e s s t o p m a j o r c o m p a n i e s t h a t o f f e r s o l u t i o n s l i k e Salesforce cust omi zati on services from o v e r - u t i l i z i n g S a l e s f o r c e c l o u d ’ s resources. B ef or e y o u u n d e r s t a n d w h a t a r e t h e r u l e s , l e t us e n l i g h t e n y o u o n w h y t h e s e e x i s t .

W h y I s There a Need f o r S a l e s f o r c e G o v e r n o r Limits?

Salesforce works i n a m u l t i t e n a n t structure. This means that each piece o f i t s software runs on a server that caters t o m u l t i p l e users at the same t i m e .

This i s better understood by comparing i t t o a v i l l a g e w e l l . Everyone uses the water i n the w e l l , but i f a couple o f f a m i l i e s overused i t , there won’t be enough t o go around. Some f a m i l i e s w i l l be l e f t w i t h l i t t l e water, w h i l e others m i g h t have t o deal w i t h g e t t i n g none at a l l !

S i m i l a r l y, the tens & thousands o f Salesforce org share a l l resources on the server. Governor l i m i t s ensure no users hog database, memory or processor resources by d i c t a t i n g the l i m i t s o f what a code can do when executed.

W h a t are Salesforce Governor Limits?

Governor l i m i t s are a set o f rules & regulations th at cap every i n d i v i d u a l user’s code t o make way f o r smooth processing. I t shuns m o n o p o l i s t i c use o f the shared resources by r e s t r i c t i n g Apex i m p l e m e n t a t i o n & runtime. For instance, on reaching the said l i m i t i n any Salesforce i n t e g r a t i o n services, i t displays an error & pauses the processes th at l e d t o i t .

There are many types o f governor l i m i t s , and a l l are associated w i t h one or a co m b i n a ti o n o f factors.

W h i l e i t d i r e c t l y ti e s some t o your Salesforce Edition, others are s t r i c t l y associated w i t h Apex programming & a f e w are l i m i t s Salesforce can change.

Understanding these l i m i t s le t s developers a r c h i t e c t t h e i r way around i t t o o ff e r the best Salesforce customization services & other results they want.

Types o f G o v e r n o r L i m i t s

a. Per-transaction Apex Limits This type o f Apex governor l i m i t counts f o r each Apex transaction. I t sets the bar at 5 0 , 0 0 0 SOQL searches f o r the maximum number o f records. The user can issue a maximum o f 2 0 SOQL queries per transaction & 150 DML statements. They can also use o n l y 100 c a l l - o u t s per transaction regardless o f i t i s HTTP requests or web service calls. I t also d i ff e r s f o r synchronous & asynchronous l i m i t s : Synchronous l i m i t - 100 SOQL queries; Overall heap size i s equal t o or less than 6MB. Asynchronous l i m i t - 2 0 0 SOQL queries; Overall heap size i s equal t o or less than 12MB.

Types o f G o v e r n o r L i m i t s

b. Per-transaction Certified Managed Package Limits Packages that have cleared the security requirements o f AppExchange are c a l l e d c e r t i f i e d managed packages. These packages have unique namespaces & are i n s t a l l e d d i r e c t l y i n t o your org from AppExchange.

Made by c e r t i f i e d Salesforce ISV partners, these have t h e i r own l i m i t s , w h i c h are often more than the usual per-transacti on l i m i t s . For example, c e r t i f i e d managed packages have 11 times more SOQL l i m i t , increasing i t s l i m i t f rom 100 t o 1,100. .

Types o f G o v e r n o r L i m i t s

c. Lightning Platform Apex Limits These l i m i t s aren’t f i x e d on Apex Transactions but instead are enforced by the Li g h t ni n g p l a t f o rm . The users are l i m i t e d t o 2 , 5 0 , 0 0 0 asynchronous Apex method executions or no. o f user licences ( i n your org) m u l t i p l i e d by 2 0 0 , whichever number i s greater. The concurrently scheduled Apex classes have a maximum cap o f 100 or 5 i n the case o f the developer e d i t i o n . .

Con c l u si on Apart f ro m these, there are s t a t i c l i m i t s , s i z e - s p e c i f i c l i m i t s & other miscellaneous l i m i t s .

The developers t hat understand these l i m i t s & f i n d a way t o work w i t h them can provide bet ter Salesforce i n t e g r a t i o n services & s i m i l a r services than others.

We at AtoCloud have developers who are w e l l versed i n everything relat ed t o Salesforce.

We o ff e r a w i d e variety o f services t o he lp you make the most out o f Salesforce.

Contact us t o get i n touch w i t h our experts.

Thank you!

Contact Us +91 9953170767 0129-4032277 contact@Atocloud.com