Loading

Salesforce Milestones Not Visible Even Though Criteria is Met

Date de publication: Jan 9, 2025
Description

There are occasions where milestones are not evaluated even if the milestone criteria are met correctly.


The milestone criteria has been met due to field updates from past milestone actions.  For example, there are two milestones in place.  The first one will be triggered first and later change the field via violation actions, which will meet the criteria of the second milestone.  It is currently working as designed.  Milestones are not evaluated by milestone actions (such as Success Actions, Warning Actions and Violation Actions).

Résolution

There are a few workarounds for this limitation:

  1. Manually edit and save the record to trigger milestones
  2. Use different criteria among milestones
  3.  Using an Apex Trigger with Queueable Class

    1. Create an Apex Trigger on Entity Update(after update)
    a. This trigger would identify if Case field is changed which should lead to Second milestone invocation
    b. If condition is applicable, it should send the id to the Queueable class

    2. Create a Queueable Apex class
     a. This class would receive the Case Id and just perform an update, without any modification

  4. Using a Scheduled Flow path
    a. Create a scheduled flow path on Case Update
    b. Specify the criteria as that of what action is performing, for eg - Case priority changing to high
    c. Have the flow run on Case: Last Modified Time and after 1 minute of update(minimum granularity possible)

 

Numéro d’article de la base de connaissances

000385782

 
Chargement
Salesforce Help | Article