salesforce case assignment rules order of execution

• Salesforce Developer

Order of execution in Salesforce

• May 9, 2023

10 Comments

In this post we will review the order of execution in Salesforce when we save a record with an insert, update, or upsert statement. This is important to understand if you are an Salesforce Admin who works on automating processes or if you are a developer that writes trigger code. Both worlds will converge in the end and affect each other, so you have to bear in mind how Salesforce executes things internally.

What is Order of Execution in Salesforce?

Order of execution in Salesforce is a set of rules that describe the path a record takes through all automation and the events that happen from SAVE to COMMIT . Before Salesforce executes these events on the server, the browser runs JavaScript validation if the record contains any dependent pick-list fields. The validation limits each dependent pick list field to its available values. No other validation occurs on the client-side.

Check our old session on “ Become an Order of Execution hero ” to walk away with an understanding of how to design robust apps optimized for scale and how to control recursion and remedy typical problems.

Lots of person struggling to remember and visualize the order of execution which starts with a DML operation and there are involvements of triggers, different types of out-of-box automation’s like process builder, workflows, flows and different rules. I hope below diagram could be easy to understand and remember taking reference.

Check latest version 56.0 here .

Order of Execution

Here is cheat-sheet of Order of execution. Salesforce performs the following events in below order.

• Loads Initial record.
• If the request came from a standard UI edit page, Salesforce runs  system validation  to check the record for page layout-specific rules, field definition, and Maximum field length.
• Executes before record-triggered flows .
• Executes  all before triggers . 
• Runs most  Custom validation .
• Executes  duplicate rules . 
• Saves  the record to the database, but doesn’t commit yet. 
• Executes  all after triggers . 
• Assignment rules . 
• Executes  auto-response rules . 
• updates the record again.
• Due to Workflow field updates introducing new duplicate field values, executes duplicate rules again. 
• If the record was updated with workflow field updates,  fires before update triggers and after update trigger one more time (and only one more time), in addition to standard validations. Custom validation rules are not run again .
• Escalation rules .
• Flows launched by processes
• Flows launched by workflow rules (flow trigger workflow actions pilot)
• Executes record-triggered flows that are configured to run after the record is saved.
• Executes  entitlement rules . 
• If the record contains  a roll-up summary field  or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure. 
• If the parent record is updated, and a  grandparent  record contains a roll-up summary field or is part of a  cross-object workflow , performs calculations and updates the roll-up summary field in the grandparent record. Grandparent record goes through save procedure. 
• Executes  Criteria Based Sharing evaluation . 
• Commits all  DML operations to the database . 
• sending email .
• asynchronous Apex jobs
• Asynchronous paths in record-triggered flows

What is part of the after commit logic?

• All email sends
• Asynchronous Apex: @future methods
• Async Sharing Rule processing (for >25,000 records)
• Outbound Messages placed on queue
• Calculate Index, such as Search Index
• Render File Previews
• Publication of Platform Events (if configured)

Operations That Don’t Invoke Triggers

• Cascading delete operations. Records that did not initiate a delete don’t cause trigger evaluation.
• Cascading updates of child records that are reparented as a result of a merge operation
• Mass campaign status changes, Mass division transfers, Mass address updates, Mass approval request transfers, Mass email actions
• Modifying custom field data types
• Renaming or replacing picklists
• Managing price books
• Changing a user’s default division with the transfer division option checked
• Update account triggers don’t fire before or after a business account record type is changed to person account (or a person account record type is changed to business account.)
• Update triggers don’t fire on FeedItem when the LikeCount counter increases.

Additional Considerations

The order of execution isn’t guaranteed when having multiple triggers for the same object due to the same event. For example, if you have two before insert triggers for Case, and a new Case record is inserted that fires the two triggers, the order in which these triggers fire isn’t guaranteed. Please implement Trigger framework for same.

Triggers and Order of Execution Video

Don’t forget to check below recording to learn about additional Considerations with some good example.

For interview questions on trigger, Check below link:

Salesforce Interview Questions on Triggers .

I hope this session helped you to understand the order of execution in Salesforce.

Amit Chaudhary

Amit Chaudhary is Salesforce Application & System Architect and working on Salesforce Platform since 2010. He is Salesforce MVP since 2017 and have 17 Salesforce Certificates.

He is a active blogger and founder of Apex Hours.

Related Posts

Check Object Permission Using Apex

Apex Sharing in Salesforce

Messaging for InApp and Web (MIAW)

I wrote a before insert trigger and a custom validation on object. Checked the debug logs. Custom validation fires first and before insert does not fire when custom validation criteria is met. So is this diagram really correct?

This correct order is Loads Initial record. If the request came from a standard UI edit page, Salesforce runs system validation to check the record for page layout-specific rules, field definition, and Maximum field length. Executes before record-triggered flows. Executes all before triggers. Runs most Custom validation. Executes duplicate rules. Saves the record to the database, but doesn’t commit yet. Executes all after triggers.

I think first before trigger gets fired and performs its operation but in custom validation steps the criteria of validation is fulfilling so you are getting an error.

Is there any difference between Flows (after save ones) and Process Builders in the order of execution?

Could you please give the details for demo process？ I don’t know how can I try the demo on my local. Thank you so much!

Which Demo you are talking about

Both of them that shown in the vedio. I want to try to do the Demos in the video myself to better understand the principles. I think your example is the most illustrative of the problem. Among all the videos I watched, you gave the best explanation.

Hi @Amit Chaudhary, I have another question: When we should conside order of execution? Or Under what circumstances or scenarios do we need to consider this function? Most of time the salesforce system designer conside and resolve it, right?

hi @Amit could you please check the commments? I think your demo is great, but I can’t try it in my org.

Leave a Reply Cancel Reply

Your email address will not be published. Required fields are marked *

Name  *

Email  *

Add Comment  *

Notify me of follow-up comments by email.

Notify me of new posts by email.

Post Comment

🎉Supercharge Your Salesforce Career with 18+ Certifications, 50+ Labs & Mock Exams. Start your FREE Trial now! 🎉

Salesforce Order of Execution: A Complete Guide

• Published on: July 16, 2023
• Updated on: February 12, 2024
• ⏱️ 7 minutes

As one of the most prominent cloud-based customer relationship management (CRM) platforms, Salesforce is renowned for its flexibility and robust features, enabling businesses to manage customer data and interactions efficiently. However, to truly maximize Salesforce’s potential, it is crucial to grasp how the platform processes the information entered by users. 

The order of execution is a vital aspect of Salesforce, referring to the sequence of events that transpire when a user performs a DML or triggers automation in Salesforce. This order defines the platform’s processing rules when handling a user’s request. Comprehending the order of execution is essential for architects, developers, administrators, and anyone working with Salesforce.

In this blog, we will delve into the Salesforce order of execution, its various stages, and its impact on the platform’s behavior.

What is the Order of Execution in Salesforce?

The order of execution refers to the sequence of events that Salesforce follows when processing a user’s request. Every time a user interacts with Salesforce, the platform follows rules to process their request. These rules are predefined and determine how Salesforce will handle the user’s input. The order of execution plays a vital role in determining the outcome of the user’s request.

Understanding the Salesforce Order of Execution Stages:

Let’s take a closer look at each stage of the order of execution and understand how it operates.

Before the events execute on the server, javascript validations are executed on the browser. After that events execute on a server in the below-given order.

Stage 1: Load the Data

Salesforce loads or initializes the record from the database. Salesforce also loads the new record with the provided new values by overriding the old values.

Stage 2: Identify the Request

Salesforce identifies the source of the request. The source can be standard UI pages, custom UI pages, SOAP Api or REST api. Based on the source of the request, different validation checks are performed.

Stage 3: Execute Record Triggered Flows

Salesforce executes Record Triggered flows which are created to run before the record is saved. 

Stage 4: Execute Before Triggers

Salesforce executes all the Before triggers i.e. before insert or before update or before delete triggers. So, any logic written in the Before triggers will execute at this stage.

Stage 5: Validate the Data

Once the Before Triggers have been executed, Salesforce will execute all the system and custom validations.

Stage 6: Duplicate Rules

After the validation, Salesforce runs the Duplicates rules on the record in context. The most important thing is if the Duplicate rules are configured with the Block action, then Order of execution will stop at this stage.

Stage 7: Save the Record

After the Duplicates rules, Salesforce will Save the record but will not commit it to the database. Record will only be committed when the record in context has successfully completed the order of execution without any failure. 

Stage 8: Execute After Triggers

After the record is saved, Salesforce executes any After Triggers i.e. after insert, after update, after delete So, any logic written in the After triggers will execute at this stage

Stage 9: Execute Assignment Rules

If the record is an object that supports assignment rules, Salesforce executes the Assignment Rules at this stage. Assignment rules specify how records should be assigned to users or queues. These rules can be based on various criteria, such as record type, region, or priority. 

Also Read – Lead Assignment Rules in Salesforce

Stage 10: Execute Auto-Response Rules

If the record is an object that supports auto-response rules, Salesforce executes the Auto-Response Rules at this stage. Auto-Response Rules specify how records should be automatically responded to, such as by sending an email or a text message. 

Stage 11: Execute Workflow Rules – If workflow field updates occur:

• Perform another update on the record.
• Re-run system validations. Note that custom validation rules , flows, duplicate rules, processes, and escalation rules will not be re-executed.
• Execute before and after update triggers once more, irrespective of whether it’s an insert or update operation, but only once.

Stage 12: Escalations Rules

If the record is an object that supports Escalation Rules, Salesforce executes the Escalation Rules at this stage. Escalation rules specify how records should be escalated to higher authorities, such as managers or executives if they are not processed within a certain time frame.

Stage 13: Execute Flows

If the record is an object that supports Lightning Flows and Processes, Salesforce executes them at this stage. The order in which Flows will execute is as per system behavior and your configuration. 

Stage 14: Execute After Record Triggered Flows

At this stage, Salesforce runs the record-triggered flows which are created to run after the record is saved.

Stage 15: Execute Entitlement Rules 

If the record is an object that supports Entitlement Rules, Salesforce executes the Entitlement Rules at this stage. 

Stage 16: Rollup Summary Fields

If the parent record or grand parent records contain rollup summary fields, then once the value is calculated the record goes through the save procedure cycle again.

Stage 17: Criteria-Based Sharing Rules

At this stage, Salesforce will check and execute all the Criteria Based Sharing Rules

for all the records in context to make sure the records are shared correctly.

Stage 18: Record Commit

After finishing all the above events on the server, Salesforce will finally commit the record in the database.

Stage 19: Post-Commit Logic

Also Read – Salesforce Trigger Frameworks: A Comprehensive Guide

Why is Understanding the Order of Execution Important?

Understanding the order of execution is essential for anyone working with Salesforce. Here are some reasons why:

• Prevent Data Loss: Understanding the order of execution can help prevent data loss. For example, suppose a user updates a record and triggers a workflow rule that updates a field. In that case, it is essential to know the order of execution to prevent overwriting the user’s input.
• Improve Performance: Understanding the order of execution can help improve performance. For example, if a user performs an action that triggers multiple workflows, it is essential to know the order of execution to optimize the workflow’s performance.
• Ensure Compliance: Understanding the order of execution can help ensure compliance. For example, suppose a user performs an action that triggers a validation rule. In that case, it is essential to know the order of execution to ensure that the data entered by the user meets the specified criteria.
• Debugging: Understanding the order of execution can help with debugging. For example, if a user performs an action that results in an error, it is essential to know the order of execution to debug the error and fix the issue.

Important Considerations and Changes from Flow Behavior  

When developing Salesforce triggers, it’s essential to be mindful of specific considerations and recent changes in flow behavior that can significantly impact how triggers operate within the Salesforce environment. These factors are critical for ensuring effective data processing and system performance.

1. Behavior of Trigger.old in Workflow Updates:

A key consideration in trigger logic is understanding how Trigger.old behaves during workflow updates. If a workflow rule updates a field after a user-initiated record change, Trigger.old retains the values from before the user update, not those altered by the workflow. For instance, if a workflow rule modifies a field post-user update, the value in Trigger.old during subsequent triggers will reflect the pre-user-update state, not the intermediate state post-workflow update.

2. Triggers in Partial DML Operations:

When a Data Manipulation Language (DML) operation allows partial success, triggers related to that operation fire with each attempt. Importantly, static variables within these triggers do not reset between attempts within the same transaction. This persistence is crucial for developers to understand when designing triggers for bulk operations and handling exceptions.

3. Execution Order of Multiple Triggers:

If there are multiple triggers on a single object for the same event, Salesforce does not guarantee their execution order. This uncertainty can lead to unpredictable results, especially if these triggers interact or depend on one another. Developers should consider this when creating multiple triggers for the same object event.

4. Changes in Flow Execution:

With newer Salesforce API versions (post 53.0), there’s a change in how after-save record-triggered flows execute concerning entitlements. In earlier versions, these flows would execute after entitlement rules. Awareness of this change is vital for those working with record-triggered flows and entitlement processes, as it affects the sequence of automation and data handling.

5. Complex Relationships and Execution Context:

For operations involving complex relationships, such as inserting non-private contacts linked to multiple accounts, the execution context and order can have nuanced behaviors. Developers should refer to Salesforce documentation specific to these use cases, like AccountContactRelation, for a deeper understanding.

6. Optimizing Opportunity Trigger Logic:

In scenarios involving Opportunity objects, especially when using before triggers to set fields like Stage and Forecast Category, there are unique considerations. Developers should familiarize themselves with the specific behaviors and best practices for Opportunity triggers to ensure correct functionality and data integrity.

By keeping these important considerations and changes in flow behavior at the forefront, Salesforce developers can design more efficient, reliable, and effective triggers. This approach not only enhances data processing accuracy but also contributes to overall system performance and stability within the Salesforce ecosystem.

Understanding the Salesforce order of execution is crucial for any developer or administrator working with the platform. It’s like knowing the game’s rules before you start playing, and it can help you avoid any surprises along the way.

By keeping in mind the different phases of the order of execution and the specific actions that take place within each one, you can optimize your code and ensure that it runs smoothly and efficiently.

If you are interested in amplifying your Salesforce skills, consider enrolling in the Salesforce Training Bootcamp Program by saasguru. Become 3X Salesforce certified and job-ready with our comprehensive program. Our graduates have witnessed an impressive average salary hike of 112%, a testament to the effectiveness of our curriculum. Start your upskilling journey with us today!

Frequently Asked Questions (FAQs)

1. why is the salesforce order of execution important.

Salesforce’s execution sequence is key for ensuring smooth operations, preventing automation overlaps, enhancing efficiency, quickly resolving issues, and maintaining data accuracy.

2. How do you remember the order of execution in Salesforce?

To better grasp Salesforce’s sequence, use these strategies: create mnemonics from phase initials, draw charts or graphs for visualization, regularly review the sequence, gain hands-on experience with real scenarios, and use prompt cards or apps for periodic knowledge testing.

Subscribe & Get Closer to Your Salesforce Dream Career!

Get tips from accomplished Salesforce professionals delivered directly to your inbox.

Looking for Career Upgrade?

Book a free counselling session with our Course Advisor.

By providing your contact details, you agree to our Terms of use & Privacy Policy

Unsure of Your Next Step?

Take our quick 60-second assessment to discover the Salesforce career path or learning journey that’s a perfect fit for you.

Related Articles

Land your dream Salesforce Financial Services Cloud (FSC) job! 40 interview questions and answers for you, covering both essential and advanced FSC concepts.

Learn how to build a standout Salesforce portfolio that showcases your skills and advances your career. Read now!

Preparing for your Salesforce Marketing Cloud Developer interview? Here are top 20 interview questions, in-depth answers, and tips to showcase your SFMC skills.

Supercharge your SaaS career

Partnership

What Is the Order of Execution in Salesforce? A Comprehensive Guide

Delve into the simplified steps of Salesforce's order of execution. This guide breaks down standard validation rules, before triggers, custom validation rules, record saving process, after triggers, flow automation, etc, to help users navigate seamless data management within Salesforce.

Krishna Teja

Salesforce, a leading customer relationship management (CRM) platform, has been transformative for businesses around the globe. But for those delving deeper into its functionalities, understanding the nuances, such as the order of execution, becomes crucial. In this guide, we'll unravel the mysteries of Salesforce's order of execution and how it can impact your Salesforce operations.

Table of Contents:

• Introduction to Order of Execution in Salesforce
• Key Components of the Salesforce Execution Process
• The Step-by-Step Order
• Common Mistakes and Best Practices
• Conclusion and Key Takeaways

1. Introduction to Order of Execution in Salesforce

When multiple automation rules, workflows, and triggers are in place, it's essential to know the sequence in which Salesforce processes them. This sequence is termed as the "Order of Execution." Knowing this order ensures data consistency and helps avoid unforeseen issues.

2. Key Components of the Salesforce Execution Process

Before we delve into the sequence, it's vital to familiarise ourselves with the primary components:

• Triggers : Custom code that performs specific actions before or after specific Salesforce operations.
• Validation rules : Rules that ensure data accuracy and consistency.
• Workflow rules : Automated processes that trigger actions based on specific criteria.
• Assignment rules : Rules that determine the assignment of new cases or leads.
• Auto-response rules : Automatic emails sent in response to lead or case creation.
• Escalation rules : Rules to escalate cases when certain conditions are met.

3. The Step-by-Step Order

Here's a simplified breakdown of Salesforce's order of execution:

• System validation : Salesforce checks for required fields, field formats, and maximum field length.
• Before Triggers : Custom code that runs before the specified Salesforce operation.
• Custom validation rules : Ensure custom criteria are met.
• After Triggers : Custom code that runs after the main Salesforce operation.
• Assignment rules : If applicable, leads/cases are assigned.
• Auto-response rules : Relevant auto-responses are sent out.
• Workflow rules : Any corresponding actions, field updates, or outbound messages are executed.
• Escalation rules : Cases are escalated if conditions are met.
• Parent Roll-up summary fields : If the record has a master-detail relationship, roll-up calculations occur.
• Criteria-based sharing evaluation (if applicable).
• Any remaining system processes .

4. Common Mistakes and Best Practices

• Not understanding the sequence : This can lead to data inconsistencies and trigger malfunctions.
• Over-relying on automation : Ensure that there's a balance between automation and manual processes for better control.
• Monitoring and testing : Always test new workflows, triggers, and rules in a sandbox environment before deploying.
• Documentation : Maintain a detailed document of all customizations and automation for future reference.

5. Conclusion and Key Takeaways

Understanding Salesforce's order of execution is pivotal for maintaining data integrity and ensuring that automated processes run seamlessly. By familiarising yourself with the sequence and monitoring your workflows, you can make the most of Salesforce's robust features.

ChatableApps

Mastering Case Assignment Rules in Salesforce – A Step-by-Step Guide for Effective Case Management

Introduction.

Effective case management is crucial for organizations that use Salesforce as their customer service platform. Salesforce offers a powerful feature called case assignment rules, which automate the process of assigning cases to the right teams or individuals. In this blog post, we’ll explore the ins and outs of case assignment rules in Salesforce and learn how they can streamline your case management workflow.

Understanding Case Assignment Rules

Case assignment rules in Salesforce are a set of criteria that determine how cases are assigned to users or queues. These rules ensure that cases are routed to the appropriate team or individual based on specific characteristics or attributes of the case. For example, you can define rules to assign high-priority cases to a specialized support team or route cases from a specific region to a regional support manager.

When a new case is created or edited, Salesforce evaluates the case assignment rules to determine the most suitable owner for the case. The rules are processed in a specified order, and the first one that matches the case criteria is applied to assign the case. It’s important to understand how these rules work and how to configure them to meet your organization’s unique requirements.

Configuring Case Assignment Rules

To access the Case Assignment Rules setup in Salesforce, go to Setup and search for “Case Assignment Rules” in the Quick Find box. This will take you to the Case Assignment Rules page, where you can create and manage your rules.

When creating or editing a case assignment rule, there are three key components to consider: rule entry criteria, assignment actions, and rule order.

The rule entry criteria define the conditions that a case must meet in order for the rule to be applied. You can specify criteria based on various attributes such as case origin, case type, case priority, or any custom fields you have added to your cases.

The assignment actions determine how the case will be assigned when the rule is applied. You can choose to assign the case to a specific user or queue, or even assign it to the case’s parent account or contact. Additionally, you can configure email notifications or escalation actions for certain cases.

It’s worth noting that you can have multiple assignment rules to handle different case scenarios. Salesforce allows you to specify the order in which these rules are evaluated. This allows for greater flexibility and ensures that cases are assigned correctly even in complex scenarios where multiple rules may apply to the same case.

In complex case assignment scenarios, you may need to use formula-based rule criteria. Formulas allow you to define more advanced conditions based on multiple attributes or calculations. This can be particularly useful when you have intricate routing requirements or need to assign cases based on a combination of factors.

Additionally, you can incorporate custom fields and objects in your case assignment rules. This means you can leverage any customizations or extensions you have made to Salesforce to tailor the assignment process to your organization’s specific needs. For example, if you have custom fields that capture region information, you can create rules to assign cases based on the region field.

Testing and Validating Case Assignment Rules

Before deploying your case assignment rules in a live environment, it’s crucial to thoroughly test and validate them. Salesforce provides several tools and best practices to help you in this process.

One effective method is to use sample test cases that cover various scenarios. Create cases that match the criteria defined in your rules and ensure that they are assigned correctly. This allows you to validate the accuracy of your rules and make any necessary adjustments.

After executing your test cases, analyze the assignment results and fine-tune your rules as needed. Keep an eye out for any unexpected or incorrect assignments and investigate the underlying rules and criteria that may have caused them. By continually monitoring and refining your rules, you can ensure the highest level of accuracy and efficiency in case assignment.

In addition to initial testing, ongoing monitoring of case assignments is vital to identify any issues that may arise. Salesforce provides reports and dashboards to help you track case assignment metrics and gain insights into potential performance bottlenecks or areas for improvement.

Optimizing Case Assignment for Efficiency

To further optimize your case assignment process, consider implementing the following best practices:

Assigning cases to queues instead of individual users: Queues allow for better load balancing and easier management of cases. Instead of assigning cases directly to individual users, create queues for different teams or roles and assign cases to these queues. This ensures that cases are distributed evenly and can be easily re-assigned if needed.

Leveraging assignment rules with round-robin or load balancing logic: If you have multiple users or teams within a queue, you can configure your assignment rules to distribute cases in a round-robin or load-balanced manner. This ensures that each user or team gets an equal share of cases and prevents any one individual from being overwhelmed with assignments.

Incorporating automated case escalation and reassignment: For certain types of cases or situations, it may be necessary to automatically escalate or reassign cases if they are not resolved within a specified timeframe. Salesforce provides workflow rules and escalation rules that can be used in conjunction with case assignment rules to automate these processes. This helps ensure that cases are promptly addressed and prevents any potential bottlenecks or delays.

Troubleshooting Common Case Assignment Issues

While case assignment rules are designed to streamline your case management workflow, there may be instances where issues arise. Here are some common problems that you may encounter and how to address them:

Identifying and resolving common assignment rule errors: Sometimes, case assignment rules may not function as expected due to incorrect configuration or conflicting criteria. It’s important to review your rule definitions and criteria to identify any potential errors and make the necessary corrections. Additionally, Salesforce provides detailed error messages and logs to help diagnose any issues that arise.

Handling conflicts and overlapping assignment criteria: In complex case assignment scenarios, it’s possible for multiple rules or criteria to match a single case. Salesforce has a built-in rule order feature that allows you to specify the evaluation order of your rules. By carefully organizing and prioritizing your rules, you can avoid conflicts and ensure that cases are assigned according to your desired logic.

Addressing performance concerns and bottlenecks: As your organization’s case volume grows, it’s essential to monitor the performance of your case assignment process. If you notice any bottlenecks or delays in case assignment, evaluate the efficiency of your rules and consider optimizing them. This may involve refining your rule criteria, reordering rules, or implementing performance enhancements such as custom indexing or caching.

Mastering case assignment rules in Salesforce is key to efficient and effective case management. By understanding the fundamentals of case assignment rules, configuring them correctly, testing and validating them thoroughly, and continuously optimizing their performance, you can streamline your case management workflow and provide exceptional customer service. Remember to regularly monitor and fine-tune your rules to ensure they align with your organization’s evolving needs. With the right approach and utilization of case assignment rules, you can enhance your customer support processes and deliver timely resolutions to your customers’ cases.

Related articles:

• Mastering Salesforce Assignment Rules – Simplifying Lead and Case Distribution
• Demystifying Assignment Rules in Salesforce – A Comprehensive Guide for Sales Success
• How to Set Up and Optimize Salesforce Assignment Rules for Enhanced Sales Team Efficiency
• The Ultimate Guide to Lead Assignment in Salesforce – Mastering Round Robin Distribution

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

An introductory guide to the Salesforce order of execution

Guest contributors.

In Salesforce, data-driven decisions and streamlined processes reign supreme. Thus, understanding the intricacies of the order of execution is paramount.

The journey begins when creating or updating a record. What happens next? When do triggers fire? How do validation rules impact the process? Answering these questions is the key to building robust processes, ensuring data integrity, and avoiding pitfalls that could compromise the efficiency of your Salesforce environment.

What is the Salesforce order of execution?

Salesforce order of execution refers to the sequence of different logic that is executed when creating, updating, or deleting a record. Salesforce has a well-defined sequence of events that occur during the processing of these actions to ensure data consistency and maintain the platform’s integrity.

However, before Salesforce executes the steps, the browser performs JavaScript validation to determine whether the record includes any dependent picklist fields. This validation restricts each dependent picklist field to its valid values. That’s the only validation on the client side.

Components of the order of execution

Salesforce’s order of execution involves various components and phases that determine the sequence in which operations, triggers, processes, and automation execute. The key components of Salesforce’s order of execution include:

• Record initialization: Salesforce loads the original record from the database or prepares a new record for an upsert operation (when rows are inserted into a database table if they do not already exist or updated if they do).
• Field value update: New field values from the request overwrite the old values.
• System validation rules: These rules enforce fundamental data integrity checks such as required fields, valid field format, maximum field length, and unique field values. In other cases, it validates only foreign keys and checks for self-referencing custom foreign keys. If multiline items exist (e.g., quote line items), Salesforce runs custom validation rules.
• Before record triggered flows: Salesforce allows you to leverage Flow Builder to declaratively create automated business logic using clicks and not code. Before record triggered flows execute before saving a record.
• Run all before triggers: Before triggers are Apex code that executes before records are saved to the database. Use before triggers to modify record data before it’s committed.
• Validation recheck: System validation repeats for required fields with non-null values. Custom validation rules are executed again.
• Duplicate rules: Duplicate rules prevent the creation of duplicate records.
• Record save: The record is saved but not committed to the database.
• Run all after triggers: An after trigger executes after any change to a record, including changes made by other triggers. For example, you could use an after trigger to automatically update related records when a record changes.
• Assignment rules: Assignment rules assign ownership of records (e.g., leads for prospective customers, or cases for after-sales service) to specific users or queues based on predefined criteria.
• Auto-response rules: Auto-response rules send automated email responses to prospects or customers based on specific conditions.
• Workflow rules with field updates: Workflow rules automate internal processes by defining criteria and executing specified actions, such as updating fields or sending email alerts. Both before and after update triggers will execute again but for the final time, irrespective of the insert or update operation on the record.
• Escalation rules: Escalation rules automatically escalate cases to higher levels of support depending on the criteria.
• Processes and flows: Processes and flows automate actions based on specified criteria. They can include both auto-launched and record-triggered processes. Processes and flows execute after before triggers.
• Entitlement rules: Entitlement rules outline the steps needed to resolve a case.
• Roll-up summary fields (parent and grandparent): If applicable, these are used to calculate and update values from related records, such as those in parent and grandparent records.
• C riteria-based sharing evaluation: Sharing rules are evaluated based on criteria.
• Database commit: All DML operations, including inserts, updates, and deletes, are committed to the database.
• Post-commit logic: Executes post-commit logic after saving changes, such as sending emails and executing asynchronous Apex jobs (e.g., queueable jobs and future methods).

You should note that steps from assignment rules to the roll-up summary field are skipped during a recursive save.

Salesforce order of execution and record locking

As various processes, triggers, and automation execute during record operations, record locking ensures that multiple users or processes don’t modify the same record simultaneously. This is because it could lead to data conflicts and inconsistencies.

When Salesforce processes updated records according to the order of execution, it takes record locking into account to prevent data conflicts. For example, when a before trigger modifies a record, it locks the record. As a result, other triggers, workflows, or processes only execute after the before trigger. Record locking ensures data consistency and prevents race conditions.

When Salesforce processes updated records according to the order of execution, it takes record locking into account to prevent data conflicts.

Troubleshooting and debugging order of execution issues

Troubleshooting order of execution in Salesforce helps ensure your automation, triggers, processes, and workflows behave as expected. Below are some steps to take when troubleshooting.

Enable debug logs

Salesforce provides debug logs that capture detailed information about the order of execution for a specific transaction. Review the debug logs to see which processes, triggers, and validations are firing and what data they are processing. Look for error messages or unexpected behavior.

Analyze error messages

If there are error messages in the debug logs or on the user interface, carefully analyze them. Error messages often provide clues about what went wrong. Pay attention to custom validation rule errors, trigger failures, or workflow rule errors.

Review trigger logic

Examine the logic within your triggers, processes, and workflows. Correctly define conditions and sequences. Check for any logical errors, infinite loops, or recursion in your Apex triggers.

Consult Salesforce community about order of operation issues

If you cannot identify the issue independently, consider seeking help from the Salesforce Trailblazer community or Salesforce support.

Best practices

Best practices for managing Salesforce’s order of execution involve optimizing your processes, triggers, and automation to ensure efficient and reliable data handling. By adhering to these practices, you can avoid conflicts, maintain data integrity, and create a more streamlined user experience.

Plan your process logic carefully

Before implementing automation, thoroughly plan the logic of your processes, triggers, and workflows. Consider the sequence of events and the impact of each action on the data. This proactive approach minimizes conflicts and unexpected outcomes.

Use bulk processing techniques

Design your triggers and processes to handle multiple records simultaneously (bulk processing). This reduces the number of times triggers and processes fire, optimizing performance, and reducing the potential for record locking.

Minimize trigger logic

Keep trigger logic focused on specific tasks and avoid unnecessary complexity. Splitting triggers based on actions (e.g., before insert, before update) can help maintain clarity and manage the order of execution.

Limit the use of recursive triggers

Recursive triggers occur when a trigger update causes another trigger to fire, leading to a loop. Use design patterns like a static variable to prevent unnecessary recursion.

Prioritize record locking best practices

Structure your automation to minimize conflicts by locking records for the shortest duration possible. Use FOR UPDATE SOQL queries to explicitly lock records when needed, ensuring that your code is aware of and respects record locks. Avoid long-running or complex operations within locked record contexts.

Structure your automation to minimize conflicts by locking records for the shortest duration possible.

Thoroughly test your automation

Before deploying automation to production, thoroughly test its behavior in a sandbox or development environment. This testing helps uncover issues related to the order of execution, logic conflicts, and performance.

Stay updated with Salesforce releases

Stay informed about new Salesforce releases and changes to the order of execution. Salesforce’s updates can introduce changes that affect your existing automation, so staying current is critical.

Wrapping up

In this comprehensive exploration of Salesforce’s order of execution, we’ve delved into its critical role in governing how triggers, workflow rules, and processes interact to maintain data integrity and streamline business operations. We’ve also explored best practices like keeping tabs on Salesforce releases and testing. Accelerate your Salesforce testing by leveraging Tricentis’s codeless automation testing solution.

This post was written by Mercy Kibet. Mercy is a full-stack developer with a knack for learning and writing about new and intriguing tech stacks.

Related resources

You may also be interested in....

3 savvy strategies for speeding up Salesforce testing

5 ways errors slip into your salesforce production environment – and how to avoid them, a guide to success with salesforce.

Case Management Best Practice Guide

Cookie Consent Manager

General information, required cookies, functional cookies, advertising cookies.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings. Privacy Statement

Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.

Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.

Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.

Cookie List

• Titan Forms
• Titan Survey
• Titan Products
• Titan Add-ons
• Knowledge Base
• Titan Academy
• Integrations
• Customer Success

Order of Execution in Salesforce

Seasoned technical writer giving you top Salesforce Tips.

What is Order of Execution in Salesforce?

The Order of Execution in Salesforce is a sequence of operations that run when a record is being saved or updated. It’s crucial for developers and administrators to understand the order of execution as it can ensure that custom code, validations, and workflows are excused in the right sequence.

What is the Order of Execution When a Case Record is Saved?

An order is followed when a Salesforce case record is saved. Developers and administrators need to know this Salesforce Order to understand how business data is manipulated and processed. When developers fully understand the order of saving a case record in Salesforce, they can confidently and accurately create different types of logic to assist all teams across an organization, such as:

Workflow Rules

Validation rules.

• Custom Triggers
• Specific Business Processes

Take a look at this standard order of execution when a case record is saved in Salesforce below as a quick guide for developers!

Order of Execution Salesforce Diagram

Step 1: Before Triggers Salesforce saving.

Step 2: Triggers

Step 3: If you have created duplicate rules on an object they will now run.

Step 4: Triggers after saving.

Step 5: If you have created assignment rules on your objects, they will be executed at this stage.

Step 6: Any definite auto-response rules will be processed here.

Step 7: Workflow rules that perform additional actions such as field updates, task creation, and email alerts. These actions can trigger additional before and after triggers.

Step 8: Any defined case escalation rules are checked and executed.

Step 9: Configured process and flows on the object will now run.

Step 10: Post-commit logic such as sending an email will run after the transaction is committed.

Step 11: Any defined roll-up summary fields defined on your object will update after the commit.

Step 12: Criteria-based sharing rules are applied after the transaction is committed to recalculate sharing.

Step 13: Schedules flows and actions are executed at this point.

Not all of the above operations will run in every transaction. Specific operations that occur depend on the actions taken and the nature of the configuration of your Salesforce instance. Understanding trigger and the order of execution can help you design an efficient and predictable business process and sequence of execution in Salesforce.

Order of Operation Rules: Flow of Execution in Salesforce

Now that we understand the flow of how the executions are run for a transaction, it is important to consider some rules and best practices when you create your own customization and Salesforce automation order of operations.

These rules ensure data integrity and consistency, they should be simple and simplistic so avoid any logic in validation rules as they run both before and after triggers.

When designing your triggers stay mindful of trigger recursion by using static variables and other techniques to ensure you don’t create an infinite loop. Your triggers should be able to handle multiple records at once so the trigger does not only run on one record at a time.

Use workflows to create simple field updates and email alerts, you should avoid creating workflows that use complex logic. Instead, delegate any complex logic to your Apex triggers or processes.

Process Builder and Flows

You can use Process Builder and Flows to automate your processes using point-and-click tools. Your processes and flows should be efficient to prevent any performance issues.

Roll-Up Summary Fields

These summary fields are used to calculate values from related records. These fields are not calculated immediately so the values may not be reflected in your real-time data.

Criteria-Based Sharing Rules

Using these sharing rules you can grant access to records based on criteria. Make sure you exercise caution when setting up sharing rules as they can expose sensitive data.

Assignment Rules and Auto-Response Rules

Assignment rules will automatically assign records to specific queues or users. Your auto-response rules will send automated responses based on specific criteria.

Trigger Execution Order Salesforce

Understanding the order in which before or after triggers are executed and designing them according to that order. The best practice for designing your triggers is using a one-trigger-per-object pattern.

Governor Limits

Governor limits impose constraints on your resources and operations in a single transaction so be sure you exercise caution when creating these. Your code should stay within these limits to prevent performance issues or exceptions.

Testing and Monitoring

Make sure you test any automation and customization you configure to ensure they work as intended. You should monitor your Salesforce test automation for performance and usage to identify and resolve any issues.

Exception Handling

Make sure you implement exception handling into your code to ensure any errors are appropriately handled and provide meaningful error messages.

Documentation and Communication

Document each step in your automation, customization, and how they interact. The changes you implement should be communicated to your team so they can note any unexpected behavior.

Understanding and adhering to these rules will help you design effective and efficient document automation within the Salesforce platform while maintaining data integrity and system performance.

Financial Order of Operations

Your Financial Order of Operations in Salesforce is a structured approach to managing your financial data. It should ensure data accuracy and consistency when handling your financial transactions.

Salesforce Data Model

First, you need to ensure you understand Salesforce’s data model including objects such as accounts, contacts, products, price books, and opportunities.

Products and Price Books

Creating and maintaining your Products and Price books is essential to ensure your product and pricing catalog is always up to date. Make sure you define the products and services that you offer, set the exact price, and group them into price books.

Opportunities

These represent potential revenue from sales or deals. Create and manage your opportunity records for each potential sale including what products the opportunity is interested in, the qualities, and expected close dates.

Using quotes you can provide pricing estimates to your customers. This can be done by linking quotes to opportunities to provide a detailed breakdown of costs and quantities to customers. You will need to track any changes made to quotes during the negotiation process.

Once your deal is confirmed, you can convert the quote into an order that will contain the finalized commitments which is important for tracking your revenue and product delivery. Your order should contain the product or service, quantity purchases, pricing, and shipping details.

Invoices and Billing

Once an order is complete, you can generate an invoice for your customers which will reflect the details of the order. You can use Salesforce’s tools to manage the billing and invoicing process .

Payments and Revenue Recognition

You can track customer payments and apply revenue recognition rules which ensures that revenue is recognized accurately based on accounting standards.

Financial Reports and Dashboards

Salesforce offers reporting and dashboard tools to generate financial reports that can be customized to meet your specific needs.

Salesforce Order of Operations: Integrations

You can integrate Salesforce with your Accounting system and other financial tools to sync your financial data and automate your accounting processes.

Compliance and Security

You will need to ensure that your financial data complies with the applicable financial regulations and that access to sensitive information is secured.

Training and Documentation

You will need to provide training to your Salesforce users, especially those you will be working with your financial data.

Continuous Monitoring and Improvement

You should always regularly review and refine your processes within Salesforce and adapt to any changing needs in your business, industry-standard changes, and compliance requirements.

The listed order can change and vary depending on your organization’s requirements and how you have customized your Salesforce. It’s important to consult your business experts during the planning and execution stages.

Using a Third-Party Tool to Make Order of Execution a Breeze

If you aren’t a coding whizz and using the other Salesforce automation tools seems daunting, you can look to the Salesforce App Exchange. Here you will find a number of trusted third-party apps that can help facilitate the automation of your Salesforce tasks. We recommend the Titan Flow tool as Salesforce flow of execution that helps you to effortlessly streamline your business processes. You can build flexible and robust flows with zero code using Titan’s easy-to-use interface . There is a trial mode for you to check out this tool before making any purchases.

Frequently Asked Questions

What is the order of execution.

Order execution is the process of accepting and completing a buy/sell order on behalf of a client. It can be carried out manually or electronically.

Why is Execution Order in Salesforce important?

Knowing the order of execution means you understand how the code, triggers, and other automation flows work within the platform. Understanding the order of execution is useful for both seasoned Salesforce developers and Salesforce newbies to maximize the potential of the platform.

What is the Salesforce order of execution between process builder and flow?

First Trigger runs and then Process Builder. Your flow triggers are executed after your workflow field updates, this includes any Apex triggers and standard validations that run as a result of the workflow field updates. Once the flow is completed, the system will execute any escalation rules.

Available on the AppExchange

It’s time to discover Salesforce’s best-kept secret and dominate the market with a powerful drag-and-drop Salesforce tool. Propel your business to new levels and succeed with automated processes using absolutely no code.

Contact us today through one of our social media channels below.

We hope to see you soon! 

Disclaimer: The comparisons listed in this article are based on information provided by the companies online and online reviews from users. If you found a mistake, please contact us.

You might be interested in these articles too

Automating Quote to Cash Processes

How to Add Bookmarks in Word

Exploring Omni-Channel & Salesforce Capabilities

Did you find these Titan Automation solutions helpful?

Get in touch and schedule a demo with Titan today to uncover the best solutions for automating business processes!

• Redline in Word
• How to Effectively Use Excel Dynamic Formula
• Proposal vs Quote and How They Differ from Other Documents
• Privacy Overview
• Strictly Necessary Cookies

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.

If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.

Best Practices for Optimizing Case Assignment Rules in Salesforce

Salesforce is a powerful customer relationship management (CRM) platform that helps businesses manage various aspects of customer interactions. One critical aspect of customer support is case management in Salesforce , where efficient case assignment rules play a vital role. Optimizing these rules can significantly enhance the effectiveness and efficiency of handling customer inquiries and issues.

Understanding Salesforce assignment rules

Salesforce assignment rules govern the distribution of incoming cases to the appropriate agents or teams. These rules ensure that each case is routed to the most suitable person for prompt resolution. Salesforce queues further facilitate this distribution by acting as virtual storage areas for cases before they are assigned.

There are two types of assignment rules in Salesforce:

• Salesforce Lead Assignment Rules primarily focus on distributing new leads among sales representatives based on predefined criteria such as geography, lead source, or lead score. 
• Case Assignment Rules are responsible for Salesforce case distribution. These rules play a pivotal role in the realm of customer support by directing incoming Salesforce support cases to agents or teams equipped with the expertise to resolve specific issues. 

As organizations strive to provide seamless experiences for both potential customers and existing clients, mastering these assignment rule types becomes crucial for optimizing customer interactions and nurturing lasting relationships.

The need for optimization

Default assignment rules might not account for specific business needs, leading to uneven case distribution, longer resolution times, and potential customer dissatisfaction. Optimizing Salesforce rules address these issues by ensuring equitable distribution, maximizing agent expertise, and expediting case resolution.

Best practices for Salesforce assignment

• Prioritizing cases . Categorize cases based on urgency or complexity to assign high-priority cases to experienced agents, ensuring quick resolutions.
• Efficient assignment techniques . Implement round-robin assignment or load-based distribution to evenly distribute cases among available agents, preventing bottlenecks.
• Role-based vs. direct assignment. Choose between role-based case assignment, where cases are directed to specific teams or direct assignment, where cases go to individual agents based on expertise.

Advanced Salesforce assignment techniques

• Multi-criteria case assignment. Combine multiple factors such as case type, priority, and customer tier for more accurate case routing.
• Automated case assignment. Leverage Salesforce automation tools like Process Builder and Flow to automate case assignments based on predefined criteria.
• Customized queues. Tailor Salesforce queues to match specific business units or case types, improving case categorization and routing.

Streamlining Salesforce case routing

Salesforce case routing logic.

Understanding Salesforce case routing logic is fundamental for ensuring that customer inquiries and issues are directed to the right personnel with the expertise to address them effectively. The case routing process involves a sophisticated interplay of various factors, such as queue membership, agent skills, workload, and availability. Salesforce’s intelligent algorithms consider these variables to determine the most suitable destination for each case, maximizing the chances of swift resolution. 

Caseload balancing

Balancing caseloads in Salesforce goes beyond equal case distribution among agents. This strategic approach boosts customer service quality and agent efficiency. Preventing overload for some and underutilization for others, it curbs burnout and enhances job satisfaction. 

Even workloads lead to swift responses, faster resolutions, and increased customer contentment. Moreover, balanced caseloads aid managers in spotting trends, optimizing resource allocation, and refining processes. This practice optimizes operations and fosters a cooperative, productive support environment.

Case escalation and reassignment strategies

Case escalation and reassignment strategies are vital for effective customer support. Escalation involves transferring cases to experienced agents or supervisors to address complex issues promptly. Case reassignment in Salesforce redirects cases to different teams or agents for specialized handling. 

These strategies prevent delays, ensure timely resolutions, and uphold customer satisfaction. With clear escalation and reassignment criteria, organizations enhance their support processes, allocate resources efficiently, and build a reputation for adeptly managing diverse customer concerns.

Configuring and customizing assignment rules

Salesforce rule configuration instructions.

• Access setup. Log in to your Salesforce account and navigate to the Setup menu located in the top-right corner of the screen.
• Search for assignment rules: In the Quick Find box, type “Assignment rules” and select what Assignment Rules you need to configure: Lead Assignment Rules or Case Assignment Rules. 
• Create a new rule. Click on the “New Assignment Rule” button to start configuring a new rule.
• Define Salesforce rule criteria. Give your rule a descriptive name and set the rule entry criteria. This includes conditions like case origin, type, priority, or other custom criteria that determine how cases are assigned.

• Specify rule actions. Determine what happens when cases meet the specified criteria. You can assign cases to specific users, queues, or use other automation processes.
• Configure rule entry order. If you have multiple assignment rules, specify the order in which they’re evaluated. This is important when cases could meet criteria for more than one rule.

• Activate the rule. Once configured, activate the assignment rule to make it live and start directing cases accordingly.

You can also integrate Salesforce workflow rules to automate follow-up actions after case assignments, enhancing customer communication.

Enhancing case management efficiency: Salesforce support cases best practices

• Utilize case templates. Expedite responses by employing predefined case templates for common issues, ensuring consistent and swift resolutions.
• Leverage macros. Enhance agent productivity with macros that automate multiple actions, reducing manual tasks and accelerating case handling.
• Opt for case cloning. Save time on data entry by cloning similar cases, streamlining the process of creating and managing new cases.
• Update Knowledge bases . Maintain accurate and current knowledge bases to empower agents with reliable information, enabling efficient issue resolution.
• Engage collaboration tools. Employ platforms like Chatter to encourage agent collaboration, fostering knowledge sharing and teamwork for complex cases.
• Notify agents of new assignments promptly and emphasize the importance of case ownership for accountability.

Optimizing case assignment rules in Salesforce is indispensable for efficient case handling. By understanding the fundamentals, implementing best practices, and embracing advanced techniques, businesses can ensure equitable case distribution, expedite resolutions, and enhance customer satisfaction. A well-optimized case assignment system ultimately streamlines support processes and contributes to the overall success of the customer support function.

Advanced Communities is your best partner when it comes to configuring your Salesforce instance or developing a Salesforce Experience Cloud site. In case of any questions feel free to reach out to get professional support when you really need it. 

You may be interested in: Maximizing ROI with Salesforce: A Case Study

Share this:

• Renewable Energy
• Artificial Intelligence
• 3D Printing
• Financial Glossary

• Onsite training

3,000,000+ delegates

15,000+ clients

1,000+ locations

• KnowledgePass
• Log a ticket

01344203999 Available 24/7

What is the Order of Execution in Salesforce

Want to develop your skills in the most efficient CRM tool to build lasting relationships with your customers? Read this blog to learn all you need to know about the Order of Execution in Salesforce, including the key steps on pre-transaction, data processing, after-transaction, and more in detail. Read more to get started.

Exclusive 40% OFF

Training Outcomes Within Your Budget!

We ensure quality, budget-alignment, and timely delivery by our expert instructors.

Share this Resource

• Salesforce Admin Training
• Oracle CRM Training Course
• Salesforce Apex Programming Language Training
• Python Course
• Microsoft Dynamics CRM Training

According to infoCleanse , 90% of Fortune 500 companies worldwide use Salesforce and only have positive reviews about it. This blog aims to provide a comprehensive overview of the Order of Execution in Salesforce, highlighting the key steps involved and their significance in the overall data processing flow.  

Table of Contents  

1) Order of Execution in Salesforce – an overview 

     a) Pre-transaction steps 

     b) Data processing steps 

     c) After-transaction steps 

2) Conclusion 

Order of Execution in Salesforce – an overview   

 The Order of Execution in Salesforce refers to the sequence of steps followed when processing data and executing operations within the platform. Understanding the order of execution is crucial for developers and administrators as it ensures the integrity and accuracy of data, as well as the proper functioning of various automation processes. 

The Order of Execution in Salesforce can be categorised into three main phases:  

a) Pre-transaction steps 

b) Data processing steps, and  

c) After-transaction steps. 

Unlock advanced CRM capabilities and master Salesforce with our comprehensive Salesforce CRM Masterclass ! Sign up now!   

The three phases can be broken down as follows: 

1) Pre-transaction steps  

This phase includes the initial steps that occur before any data processing takes place. It sets the context for the transaction and prepares the application for further processing. 

a) User Interface (UI) request : The order of execution begins when a user interacts with the Salesforce user interface, initiating a request for data or action. This request determines the scope of the transaction and the objects involved. 

b) Application initialisation : After the UI request, Salesforce initialises the application by loading the necessary metadata and configuration settings. This ensures that the application environment is ready for subsequent processing. 

c) Validation rules : Validation rules are applied to the data entered or modified by the user. These rules evaluate the data against predefined criteria to ensure its accuracy and integrity. If the data fails validation, error messages are displayed to the user. 

2) Data processing steps  

This phase involves the processing of data and the execution of various operations based on the pre-transaction setup. 

a) Before triggers : Before triggers are executed, before any records are saved to the database. They allow developers to perform custom actions or manipulate data before it is committed. 

b) Custom validation rules : Custom validation rules, distinct from the initial validation rules, are executed after the before triggers. These rules provide additional checks on the data based on specific business requirements. 

c) Duplicate rules : Duplicate rules help identify and prevent the creation of duplicate records. They compare the new record being created or modified with existing records and enforce duplicate management policies. 

d) Data enrichment : Data enrichment processes, such as address standardisation or data cleansing, can be performed at this stage. These processes enhance the quality and completeness of data stored in Salesforce. 

e) Before save updates : Before save updates are performed after data enrichment and before the system validation rules. They allow developers to update related records or perform calculations based on the changes made to the data. 

f) System validation rules : System validation rules check the data against various system-level requirements and restrictions. These rules ensure data integrity and compliance with Salesforce platform limits and configurations. 

g) Auto-response rules : Auto-response rules are triggered when specific criteria are met, such as incoming emails or web-to-case submissions. They automate the process of sending predefined responses to users or customers. 

h) Workflow rules : Workflow rules define specific criteria and actions to be executed when the requirements are met. They automate repetitive tasks and streamline processes within Salesforce. 

i) Escalation rules : Escalation rules define criteria for escalating cases or records to higher levels of management. They ensure the timely resolution of critical issues or essential tasks. 

j) Assignment rules : Assignment rules, if not applied earlier, are executed at this stage to assign records to appropriate users or queues based on specified criteria. 

k) Post-template processing : If email templates are used, Salesforce performs post-template processing by merging the template with the data and sending the email to the intended recipients. 

l) Processes : Processes, such as record updates or creation, can be automated using Salesforce Process Builder. These processes allow businesses to define complex workflows and execute actions based on specific triggers. 

Gain the essential knowledge to master Salesforce administration with Salesforce Admin Training . Register now!  

3) After-transaction steps    

This phase includes the steps that occur after the data processing is complete and the changes have been saved to the database. 

a) DML operations : After the database commit, additional data manipulation language (DML) operations, such as record updates or deletions, can be performed. 

b) Email services : Email services in Salesforce enable integration with external systems through email communication. This step processes incoming and outgoing emails and executes the configured actions. 

c) Outbound messages : Outbound messages are used to send notifications or data updates to external systems in real time. They are triggered after the DML operations and provide seamless integration. 

d) Workflow time-dependent actions : Workflow time-dependent actions are executed based on time triggers defined in workflow rules. They schedule specific actions or notifications at predefined intervals. 

e) Approval processes : If an approval process is defined for the records, Salesforce applies it during this step. Approval processes facilitate the review and approval of records by designated users or groups. 

f) Post-commit logic : Post-commit logic includes actions or processes that need to be executed after the database commit operation. This phase allows developers to perform additional operations based on the saved data. 

g) Sending email : The final step in the order of execution is sending any pending email notifications, including workflow emails, approval-related emails, or custom email alerts. 

Become an expert app builder and unlock the power of Sales platform development. Register now for our Salesforce Platform App Builder Training !  

Conclusion  

Understanding the Order of Execution in Salesforce is crucial for developers and administrators to ensure the accuracy and integrity of data. By following the predefined sequence of steps, Salesforce maintains consistency and allows customisation at various stages of the data processing flow. By clearly understanding each step and its significance, you can build efficient and reliable applications on the Salesforce platform. 

Boost your digital CRM skills with comprehensive CRM Training courses . Sign up today!  

Frequently Asked Questions

Upcoming programming & devops resources batches & dates.

Tue 21st May 2024

Tue 23rd Jul 2024

Tue 1st Oct 2024

Tue 26th Nov 2024

Get A Quote

WHO WILL BE FUNDING THE COURSE?

My employer

By submitting your details you agree to be contacted in order to respond to your enquiry

• Business Analysis
• Lean Six Sigma Certification

Share this course

Our biggest spring sale.

We cannot process your enquiry without contacting you, please tick to confirm your consent to us for contacting you about your enquiry.

By submitting your details you agree to be contacted in order to respond to your enquiry.

We may not have the course you’re looking for. If you enquire or give us a call on 01344203999 and speak to our training experts, we may still be able to help with your training requirements.

Or select from our popular topics

• ITIL® Certification
• Scrum Certification
• Change Management Certification
• Business Analysis Courses
• Microsoft Azure Certification
• Microsoft Excel Courses
• Microsoft Project
• Explore more courses

Press esc to close

Fill out your  contact details  below and our training experts will be in touch.

Fill out your   contact details   below

Thank you for your enquiry!

One of our training experts will be in touch shortly to go over your training requirements.

Back to Course Information

Fill out your contact details below so we can get in touch with you regarding your training requirements.

* WHO WILL BE FUNDING THE COURSE?

Preferred Contact Method

No preference

Back to course information

Fill out your  training details  below

Fill out your training details below so we have a better idea of what your training requirements are.

HOW MANY DELEGATES NEED TRAINING?

HOW DO YOU WANT THE COURSE DELIVERED?

Online Instructor-led

Online Self-paced

WHEN WOULD YOU LIKE TO TAKE THIS COURSE?

Next 2 - 4 months

WHAT IS YOUR REASON FOR ENQUIRING?

Looking for some information

Looking for a discount

I want to book but have questions

One of our training experts will be in touch shortly to go overy your training requirements.

Your privacy & cookies!

Like many websites we use cookies. We care about your data and experience, so to give you the best possible experience using our site, we store a very limited amount of your data. Continuing to use this site or clicking “Accept & close” means that you agree to our use of cookies. Learn more about our privacy policy and cookie policy cookie policy .

We use cookies that are essential for our site to work. Please visit our cookie policy for more information. To accept all cookies click 'Accept & close'.

SalesforceBlue

Feel the rhythm of Salesforce

Order Of Execution In Salesforce Simplified

Suppose you are told to bring groceries from the supermarket. You will first get the list of items to bring up, take your car or walk to the supermarket, purchase & pay for the goods and drive or walk back home.

In the above example, you were following a specific order to bring up the goods back to your home. Similarly, a salesforce transaction follows up a specific order for doing a series of execution which are as follows (as of writing):

• Loads the original record from the database or initializes the record for an  upsert  statement.
• Compliance with layout-specific rules
• Required values at the layout level and field-definition level
• Valid field formats
• Maximum field length When the request comes from other sources, such as an Apex application or a SOAP API call, Salesforce validates only the foreign keys. Before executing a trigger, Salesforce verifies that any custom foreign keys don’t refer to the object itself. Salesforce runs custom validation rules if multiline items were created, such as quote line items and opportunity line items.
• Executes record-triggered flows that are configured to run before the record is saved.
• Executes all  before  triggers.
• Runs most system validation steps again, such as verifying that all required fields have a non- null  value, and runs any custom validation rules. The only system validation that Salesforce doesn’t run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.
• Executes duplicate rules. If the duplicate rule identifies the record as a duplicate and uses the block action, the record isn’t saved and no further steps, such as  after  triggers and workflow rules, are taken.
• Saves the record to the database, but doesn’t commit yet.
• Executes all  after  triggers.
• Executes assignment rules.
• Executes auto-response rules.
• Updates the record again.
• Runs system validations again. Custom validation rules, flows, duplicate rules, processes, and escalation rules aren’t run again.
• Executes  before update  triggers and  after update  triggers, regardless of the record operation (insert or update), one more time (and only one more time)
• Executes escalation rules.
• Flows launched by processes
• Flows launched by workflow rules (flow trigger workflow actions pilot)When a process or flow executes a DML operation, the affected record goes through the save procedure.
• Executes record-triggered flows that are configured to run after the record is saved.
• Executes entitlement rules.
• If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure.
• If the parent record is updated, and a grandparent record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the grandparent record. Grandparent record goes through save procedure.
• Executes Criteria Based Sharing evaluation.
• Commits all DML operations to the database.
• Sending email
• Enqueued asynchronous Apex jobs, including queueable jobs and future methods
• Asynchronous paths in record-triggered flows

Note: During a recursive save, Salesforce skips steps 9 (assignment rules) through 17 (roll-up summary field in the grandparent record).

Here is the reference for the order of execution: Official Docs For Order Of Execution

Thank you for visiting SalesforceBlue.com If you have any queries feel free to write down a comment below 🙂

• Apex DML Statements Simplified
• Apex Triggers Simplified

You May Also Like

Apex Unit Tests Simplified

Apex SOQL FOR UPDATE

Salesforce Apex Flex Queue

Leave a reply cancel reply.

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

• Marketing Cloud

Experiences

Access Trailhead, your Trailblazer profile, community, learning, original series, events, support, and more.

Search Tips:

• Please consider misspellings
• Try different search keywords

Triggers and Order of Execution

When you save a record with an insert , update , or upsert statement, Salesforce performs a sequence of events in a certain order.

Before Salesforce executes these events on the server, the browser runs JavaScript validation if the record contains any dependent picklist fields. The validation limits each dependent picklist field to its available values. No other validation occurs on the client side.

For a diagrammatic representation of the order of execution, see Order of Execution Overview on the Salesforce Architects site. The diagram is specific to the API version indicated on it, and can be out-of-sync with the information here. This Apex Developer Guide page contains the most up-to-date information on the order of execution for this API version. To access a different API version, use the version picker for the Apex Developer Guide .

On the server, Salesforce performs events in this sequence.

• Loads the original record from the database or initializes the record for an upsert statement.

Salesforce performs different validation checks depending on the type of request.

• Compliance with layout-specific rules
• Required values at the layout level and field-definition level
• Valid field formats
• Maximum field length

Additionally, if the request is from a User object on a standard UI edit page, Salesforce runs custom validation rules.

• For requests from multiline item creation such as quote line items and opportunity line items, Salesforce runs custom validation rules.
• For requests from other sources such as an Apex application or a SOAP API call, Salesforce validates only the foreign keys and restricted picklists. Before executing a trigger, Salesforce verifies that any custom foreign keys don’t refer to the object itself.
• Executes record-triggered flows that are configured to run before the record is saved.
• Executes all before triggers.
• Runs most system validation steps again, such as verifying that all required fields have a non- null value, and runs any custom validation rules. The only system validation that Salesforce doesn't run a second time (when the request comes from a standard UI edit page) is the enforcement of layout-specific rules.
• Executes duplicate rules. If the duplicate rule identifies the record as a duplicate and uses the block action, the record isn’t saved and no further steps, such as after triggers and workflow rules, are taken.
• Saves the record to the database, but doesn't commit yet.
• Executes all after triggers.
• Executes assignment rules.
• Executes auto-response rules.

This sequence applies only to workflow rules.

• Updates the record again.
• Runs system validations again. Custom validation rules, flows, duplicate rules, processes, and escalation rules aren’t run again.
• Executes before update triggers and after update triggers, regardless of the record operation (insert or update), one more time (and only one more time)
• Executes escalation rules.
• Flows launched by processes
• Flows launched by workflow rules (flow trigger workflow actions pilot)

When a process or flow executes a DML operation, the affected record goes through the save procedure.

• Executes record-triggered flows that are configured to run after the record is saved
• Executes entitlement rules.
• If the record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the parent record. Parent record goes through save procedure.
• If the parent record is updated, and a grandparent record contains a roll-up summary field or is part of a cross-object workflow, performs calculations and updates the roll-up summary field in the grandparent record. Grandparent record goes through save procedure.
• Executes Criteria Based Sharing evaluation.
• Commits all DML operations to the database.
• Sending email
• Enqueued asynchronous Apex jobs, including queueable jobs and future methods
• Asynchronous paths in record-triggered flows

During a recursive save, Salesforce skips steps 9 (assignment rules) through 17 (roll-up summary field in the grandparent record).

Additional Considerations

Note these considerations when working with triggers.

• If a workflow rule field update is triggered by a record update, Trigger.old doesn’t hold the newly updated field by the workflow after the update. Instead, Trigger.old holds the object before the initial record update was made. For example, an existing record has a number field with an initial value of 1. A user updates this field to 10, and a workflow rule field update fires and increments it to 11. In the update trigger that fires after the workflow field update, the field value of the object obtained from Trigger.old is the original value of 1, and not 10. See Trigger.old values before and after update triggers.
• If a DML call is made with partial success allowed, triggers are fired during the first attempt and are fired again during subsequent attempts. Because these trigger invocations are part of the same transaction, static class variables that are accessed by the trigger aren't reset. See Bulk DML Exception Handling .
• If more than one trigger is defined on an object for the same event, the order of trigger execution isn't guaranteed. For example, if you have two before insert triggers for Case and a new Case record is inserted. The firing order of these two triggers isn’t guaranteed.
• To learn about the order of execution when you insert a non-private contact in your org that associates a contact to multiple accounts, see AccountContactRelation .
• To learn about the order of execution when you’re using before triggers to set Stage and Forecast Category , see Opportunity .
• In API version 53.0 and earlier, after-save record-triggered flows run after entitlements are executed.
• Salesforce Help : Triggers for Autolaunched Flows

Salesforce Geek

Let's Learn Apply and Share

Order of execution in Salesforce

In this blog post, we will understand the concept of Salesforce’s Order of Execution and why it is important in the Salesforce ecosystem.

What is the Order of Execution of Salesforce?

Whenever you create or modify a record in Salesforce, a set of events, called the Order of Execution, starts work. This sequence checks and governs all the interactions between different automation and functionalities as they affect the record, starting from the moment you click save until the changes are finalized.

Salesforce as a multi-tenant architecture:

Salesforce architecture is quite popular due to its multitenancy. Many customers use the same server configuration that makes it cost-effective but their data is safely separate, which means each client’s information remains protected and separate from other clients.

Multi-tenancy enables any developer to create an application, host it to the cloud, and quickly share it with many clients. In addition, the developers can update the offered software in a single location and all users of the application will receive the latest version.

Salesforce ensures that each organization’s operations are carried out without interference from others and within the allocated resource limits. Salesforce’s multitenant architecture stores all client data in a single database. In terms of governor limits, Salesforce’s multi-tenant architecture helps enforce these limits by ensuring fair resource allocation among all organizations.

Flow of Execution

Load & Prepare Data:

Salesforce retrieves the original record (update) or initializes a new one (upsert). New field values overwrite existing ones.

Standard Validations (UI Edits Only):

The system checks for layout rules, required fields, valid formats, and maximum field lengths (applicable only for edits from the standard UI).  For other sources like APIs and Apex, only foreign keys are validated.

App Initialization:

Application initialization involves gathering all the necessary information about how things should work for your specific task. It loads the metadata, which acts like a blueprint, and configuration settings that define how the application should function in this situation.

Custom Validations:

Salesforce executes any custom validation rules that you’ve defined.

Record-triggered flows (before save)

Record-triggered flows can run at two specific points in the Salesforce record save process i.e Before Save and After save.

Before Triggers:

When you write custom Apex code, it executes before the record is saved. This provides an opportunity for manipulating data or conducting pre-save validations.

Validations & Duplicate Rules:

Standard validations (except layout rules for UI edits) run again. Salesforce actively checks for duplicate records using defined rules, if a duplicate is found and the “block” action is set, the system prevents the record from being saved.

Save (Uncommitted):

Salesforce saves the modified record to the database temporarily, not permanently.

After Triggers:

After saving the record, Salesforce triggers your custom Apex code, allowing for post-save actions.

Assignment & Auto- Response Rules:

Assignment rules assign the record to the appropriate owner. Auto-response rules trigger actions like sending emails based on record changes. Workflow rules execute field updates, notifications, or other actions based on defined criteria.

Workflow Field Updates (if applicable):

If workflow rules update fields, the record is saved again. Before and after update triggers fire one more time (only once) for these updates. Custom validations, duplicate checks, and escalation rules are not repeated.

Escalation & Entitlement Rules:

Escalation rules can be triggered based on record changes. Entitlement rules may also execute (depending on your setup).

Processes & Flows:

When a workflow rule triggers an action, it can launch a process or flow. These processes or flows might update records again, potentially leading to additional automated actions.

Roll-up Summary Updates:

For records with roll-up summary fields or those involved in cross-object workflows, Salesforce actively calculates and updates these fields in parent or even grandparent records. These parent/grandparent records then go through their save procedures.

Criteria-Based Sharing:

When saving a record, Salesforce checks criteria-based sharing rules to determine who can see each record.

DML Operations:

DML (data manipulation language) allows you to make additional updates or deletions to related records, even after you’ve saved the initial changes.

Commit & Post-Commit Actions:

Salesforce permanently saves all changes to the database (commits) and then executes post-commit actions like outbound messages and sending emails,

Why do we need an Order of Execution in Salesforce?

By understanding this order, you can ensure the smooth functioning of your automation, maintain data integrity, and build reliable applications on the Salesforce platform.

Data Integrity: It plays a crucial role in maintaining the accuracy and consistency of your data. By following the sequence, the system prevents conflicts that may arise if different automations attempt to modify the same data simultaneously. For instance, a validation rule might disallow saving a record with missing data, even if a workflow rule attempts to update that missing field later in the process.

Predictable Behavior: Understanding the order ensures that your automation (such as triggers and workflows) executes in the sequence. This predictability enables you to build reliable automation that achieves the desired outcomes without any unexpected interruptions or errors.

Efficient Automation: The order allows for optimized automation workflows. If you know when specific actions occur, you can trigger them at the perfect moment to optimize the process .   For example, We can send an email notification after the record is saved and all validations are complete.

Reduced Errors:   The defined order prevents conflicts that might arise from overlapping actions. Let’s say one automation calculates a field value just before saving, and another tries to update it afterward. This could cause Conflicts. The order avoids this issue by ensuring a clear sequence of execution.

Troubleshooting Issues: If you encounter problems with your automation, understanding the order of execution can help you pinpoint the source of the issue. By knowing when specific actions occur, you can trace the flow of data and identify where things might be going wrong.

Also, Learn more about  The Future of User Access Management in Salesforce

1 . What is the order in which Salesforce executes events when we save a record? 

Saving a record in Salesforce triggers a specific sequence: 1. Validations (ensure data meets criteria). 2. Triggers & workflows (customizable actions before/after save). 3. System actions (assignments, emails, final data processing).

2. Which will execute the first process builder or flow in Salesforce?

In Salesforce, Flow executions take priority over Process Builder. Process Builder helps you to initiate flows but flows can not directly trigger Process Builders. This means Flows generally execute first, offering more power and flexibility for automation.

3 . Which executes the first trigger or flow?

In Salesforce, Salesforce executes record-triggered flows specifically configured to run before the record is saved.  After the record-triggered flows, Salesforce executes all before triggers.

From this blog, we can get to know that Salesforce doesn’t just blindly save your records! It follows a specific order, called the Order of Execution, to process data and ensure everything runs smoothly. This order dictates the sequence of various actions, like validation rules, workflows, triggers, and database updates. Understanding this sequence is crucial for optimizing how Salesforce operates and maximizing its efficiency.

Get a complete Roadmap To Learn Salesforce Admin And Development

Neelu Mahto

Neelu is pursuing her career in the Salesforce domain. She believe that words are powerful tools, and she love using them to express herself, both in technical and creative ways. This passion for language makes her a bit of a logophile (a lover of words!). In her free time, she enjoy crafting quotes to share her thoughts and inspirations.

Similar Posts

Use Responsive Web Forms for Salesforce Lead Generation

Salesforce Integration Roadmap for Beginners

Leave a reply cancel reply.

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

Blog Posts Downloadable Resources Infographics

Order of Execution (Rules, Triggers etc.) in Salesforce & Debug Log

Salesforce has a bunch of rules that can be defined on objects and fields. For example, you can define validation rules, workflow rules, process builder, flows, assignment rules, escalation rules, auto-response rules, triggers etc.

Whether you are an administrator, consultant, developer, or architect – it is important for you to understand the order in which these rules and triggers are executed.

The following picture depicts the order of execution visually. (For finer details, please refer to the Apex Developer Guide URL mentioned under ‘ References & Useful URLs ‘ section below).

Not an “All Access” Pass Member Yet?

Get Download Access to this & 150+ More Step-by-Step Guides with “All Access” Pass. A simple and single plan to access our entire library of courses, guides, workshops & masterclasses on Salesforce.

Now, at times things will not work as you expect it to. Your system may behave like a drunk (or at least you would think so). In such cases ‘Debug Logs’ feature in Salesforce will come to your rescue. 

Let’s say that we have configured the following on Lead object

• There is a validation rule on the lead object that states that if the lead rating is hot, the email cannot be blank
• Then we have configured duplicate rules in Salesforce to ensure that the lead being created does not already exist
• Then there is a Lead assignment rule defined in Salesforce that assigns all “Hot” leads to the user “Nick Admas”.
• Then there is a workflow rule with field update action defined that sets the Industry picklist field of Lead to “Technology” if City is San Francisco.
• Next, there is a Process Builder with criteria if Lead Status is “Site Visit’ then a Site Visit record should be created automatically mapping values from Lead.

If you are using a combination of different features in Salesforce and running into issues where the system is not behaving the way you expect it to, the best way to diagnose and troubleshoot will be to turn the debug on (Setup -> Debug Logs), execute the transaction and then check the debug log. Based on the example given above, here is what you will see in the debug log (hover on these images to enlarge).

Keep this sequence in mind while designing your solution and your app will behave properly.

(By the way if you are preparing for Platform Developer Certification, there are a couple of questions on the order of execution)

References & Useful URLs

• Triggers and Order of Execution – Apex Developer Guide (15 mins) – https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm
• Blog Post – Monitoring & Auditing Tools in Salesforce

Other Related posts:

• Validation Rules Examples in Salesforce
• How to handle junk / spam leads in Salesforce
• My Top 10 Salesforce Blog Posts of 2020
• Step By Step Guide to Using Restriction Rules in Salesforce
• Step By Step Guide To Creating Record-Triggered Flow in Salesforce

32 thoughts on “Order of Execution (Rules, Triggers etc.) in Salesforce & Debug Log”

Hi All, Anyone can please help me that above steps are correct but are they mentioned in Salesforce release notes?. I can check the given steps on one of the knowledge article of salesforce but didn’t find anything in release notes.

H Vishal, the order of execution is not mentioned in the release notes. You can find it in Apex Developer Guide -> Triggers and Order of Execution at URL https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_triggers_order_of_execution.htm

Thanks its helpful and good explanation.

My pleasure Nezam 🙂

This order appears to no longer be valid. Spring 20 introduced Before Save Update Flows that run prior to the before triggers. This would also mean step 10 would need to be updated in the process as flows are running at a different time.

Hi Dennis, thanks for your feedback. The order has now been updated based on the Winter ’21 release of Salesforce.

That is a great way to memorize the sequence. thank you Agarwal!

Thanks, Tulasi.

Thanks Tulasi

what about process builder

Duplicate rules?

Just Awesome 🙂

very well explaned…..For KT

after field update coz of WR, only BT and AT will fire but no SV, CV, AR, ARR, and WR. Correct ?

Very well explained

It is Well Explained

Was wondering where cross object formula’s come into play and this was an enormous help ! Awesome job.

Thanks Morvana, Glad that it helped

If Before trigger fails then, what happen to rest of execution.Whether it will stop other execution or it will execute the remaining process?

It Helps me alottttt…. Thanx, ashish

Thanks a lot. Its very useful

You left out several important points – like when the records(s) are soft written to the database and then eventually committed to the DB.

It’s critical to understand that the before triggers are b/4 the write to the database and ther after triggers are after the write to the database but before the committ.

Thanks. Good to remember this one.

very helpful post. Is this true though – If a validation rule throws an error (i.e. the Validation Rule is working as designed), the BeforeUpdate code will get thrown away (e.g. if our BeforeUpdate code is supposed to create new Opportunity when changing Stage).

This helped me a lot. 🙂

Glad to know that it was helpful Eugene !

Good article, clear explanation

That is very well explained

Thanks Ashish !

Leave a Comment Cancel Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed .