Salesforce Governor Limits

• • Ensure fair resource distribution among organizations.
  • Maintain system performance and reliability.
  • Prevent infinite loops or excessive resource consumption.

Salesforce enforces different types of limits based on usage. Here are some of the key Governor Limits you should be aware of:

• Maximum 100 SOQL queries per transaction in synchronous Apex.
• Maximum 200 SOQL queries per transaction in asynchronous Apex.
• Solution: Use bulk processing and avoid SOQL queries inside loops.

• Maximum 150 DML statements per transaction.
• Solution: Use bulkified operations and group records in a single DML statement.

• Maximum 10 second of CPU execution time transation.
• Solution : Optimize loops, reduce unnecessary computations, and avoid nested loops.

• Maximum 6 MB for synchronous transactions.
• Maximum 12 MP for asynchronous transactions.
• Solution: Use transient variables and avoid storing large data sets in memory.

• Maximum 50 future method call per transaction.
• Solution: Use batch Apex when processing large data volumes.

• Maximum 100 callouts per transaction (HTTP requests to external services).
• Soluction: Optimize external API calls and use continuations where possible.

• Salesforce limits how many triggers can execute per transaction.
• Solution: Use Trigger Framework to manage execution efficiently.

• Maximum 5,000 emails per day for organization-wide emails.
• Solution: Use email services or third-party solutions like Marketing Cloud for large-scale emails.

• Always use lists instead of single record operations.
• Use FOR loops efficiently and avoid queries inside loops.

• Use maps and sets to handle large data processing efficiently.

• Use selective queries and filter data as much as possible.
• Use relationship queries (JOINs) instead of multiple SOQL queries.

• Move heavy computations to Batch Apex, Queueable Apex, or Future methods.

• Store frequently used data in custom settings or custom metadata.
• Use @Transient variables in Visualforce controllers to reduce heap size.

• Use the Developer Console, Debug Logs, and Governor Limits API to monitor and analyze limit usage.

• Use flows, process builder, and declarative tools where possible instead of Apex.