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

Hello, I am having issues with multiple email notifications when a case is submitted to a queue.

When a case is submitted to our internal SF queue the case will fire multiple duplicate noifications for the one case that was submitted. Sometimes it does this at random on other cases submitted to other queues. I logged a case with saleforce support and after running a debug log they got the following results...

When I was working with the debug log which I have set up https://edgenet.my.salesforce.com/p/setup/layout/ApexDebugLogDetailEdit/d?retURL=%2Fsetup%2Fui%2FlistApexTraces.apexp&apex_log_id=07L3600000bFqXtEAK and when I searched with the test case id I created “5003600000caZvY” and if you see the debug log if you search from “10:35:48.501 ” you will notice that it says “{!ID:00N3600000SwGa2} = "Lowe's Professional Services")|Values:Case_Owner_Text__c=Adria Heimburger 10:35:48.501 (4535835185)|WF_CRITERIA_END|false 10:35:48.501 (4535870098)|WF_CRITERIA_BEGIN|[Case: 00070803 5003600000caZvY]|Case Status - Lowes Closed-Escalated|01Q36000000Ue6S|ON_CREATE_OR_TRIGGERING_UPDATE|0 10:35:48.501 (4552316493)|WF_RULE_FILTER|[Case : Status equals Closed-escalated“ and it continues. This means that the record type when changed id does not met criteria .

Moving further from “10:35:48.798” you will see that the trigger is taking interference here while execution along with the Validation rules (here are its id)
1. 03d36000000Npde
2. 03d36000000NpdZ
3. 03d36000000Npdt
4. 03d36000001Q9Qe
5. 03d36000001Lzj8
6. 03d360000015s1v

Would any of this be the cuase of the error? If so what should be done to correct this.