Apex Code Development You need to sign in to do that
Don't have an account?
sfdcdude Issue in Reevaluate workflow rules
Hi Team,
I have a scenario where, I need to send email alerts after 1 hour continuously till the status will get change from A to B.
We know that we do not have option to schedule an alert daily by using wrokflow rules. but some workaround (https://salesforce.stackexchange.com/questions/221834/email-alter-to-everyday-using-time-dependent-workflow-action-in-salesforce) I have found and did the same.
It is working upto some extent and my issue here is......
Lets say my 5 records email alert scheduled 5:00 PM after meeting criteria.
When I change any of the record from A to B at 6:00 PM this particular record related alert is going away from the scheduled queue which is expected. But, this record related updated time (6:00 PM) is effecting for the rest of the 4 records too.
Please help me here to resolve this issue.
I have a scenario where, I need to send email alerts after 1 hour continuously till the status will get change from A to B.
We know that we do not have option to schedule an alert daily by using wrokflow rules. but some workaround (https://salesforce.stackexchange.com/questions/221834/email-alter-to-everyday-using-time-dependent-workflow-action-in-salesforce) I have found and did the same.
It is working upto some extent and my issue here is......
Lets say my 5 records email alert scheduled 5:00 PM after meeting criteria.
When I change any of the record from A to B at 6:00 PM this particular record related alert is going away from the scheduled queue which is expected. But, this record related updated time (6:00 PM) is effecting for the rest of the 4 records too.
Please help me here to resolve this issue.
It actually means to re-evaluate ALL Active workflows after the Field Update. It is used in situations where the Field Update you are making could cause a Workflow Rule that didn't apply to the current record suddenly apply to the current record.
Since you can't control the order that Workflow Rules run on an object, this gives a chance to 'check again' after the Field Update
Refer this discussion:
https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000A85eDSAR
If you still think this is not working as intended then please reach out to Salesforce support by raising a case and explaining the concern with support engineer, our extended team could help you understand this better and report any unwanted behavior with product teams.
Hope above information helps. Please mark as Best Answer so that it can help others in future.
Thanks.