Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>@grigriforce beat me to the punch - I would also suggest using a field to count the number of retries, rather than a simple boolean value. Here's a "bulkified" trigger with essentially the same logic as the one you posted:</p> <pre><code>trigger trgBouncedEmails on EmailMessage (after insert) { List&lt;Id&gt; parentCaseIds = new List&lt;Id&gt;(); for ( EmailMessage myEmail : trigger.New ) { // mail box full bounced email for Financial Review emails if ( myEmail.HtmlBody.contains('full') &amp;&amp; myEmail.Subject.contains('Financial Review') ) parentCaseIds.add(myEmail.ParentId); } Case[] parentCases = [select c.Id from Case c where c.Id in :parentCaseIds]; for ( Case c : parentCases ) { c.Resend_Email_Count__c += 1; // this will trigger workflow to send the email again c.Resend_Email_Time__c = System.now(); // keep track of when it was last retried } update parentCases; } </code></pre> <p>Update to space emails out evenly over a 24-hour period:</p> <p>Rework your workflow to make sure it has been 8 hours since <code>Resend_Email_Time__c</code> was last set, and then schedule an Apex job to run every hour to pick up eligible Cases that need to have their emails resent, and call update on them to make sure the workflow doesn't go too long without firing:</p> <pre><code>global class ResendCaseEmails implements Schedulable { global void execute(SchedulableContext sc) { Contact[] cs = [select id, Resend_Email_Count__c, Resend_Email_Time__c from Contact where Resend_Email_Count__c &lt; 4]; List&lt;Contact&gt; ups = new List&lt;Contact&gt;(); for ( Contact c : cs ) { if ( c.Resend_Email_Time__c != null &amp;&amp; c.Resend_Email_Time__c.addHours(8) &lt; System.now() ) ups.add(c); } update ups; } } </code></pre> <p>**note that it's not a best practice to have this code in the class that implements Schedulable - this code would ideally be in another class that is called by the <code>ResendCaseEmails</code> class.</p> <p>You can schedule this job to run once an hour by calling this code from the developer console:</p> <pre><code>ResendCaseEmails sched = new ResendCaseEmails(); String cron = '0 0 * * * ?'; System.schedule('Resend Case Email Job', cron, sched); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POBounce email handling mailbox full using salesforce triggers
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJCD
    1. USJCD
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBounce email handling mailbox full using salesforce triggers
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COIm sorry I didnt include this in my question, but I need to resend 3 times in the frequency of 24 hrs, do you have an idea how to keep track of that?>
      singulars
      1. PO
      1. USraym0nd
    2. CO@raym0nd Is the problem that you aren't able to guarantee that the 3 retries are within the initial 24 hour period, or that you want it to try 3 more times in each subsequent 24 hour period until it is received successfully?
      singulars
      1. PO
      1. USJCD
    3. COThe problem is that the above code keeps trying indefinitely until the message is received, what I have to do is to make it that it only tries 3 times in a 24 hrs period then stops resending.
      singulars
      1. PO
      1. USraym0nd
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload