I have a time-based workflow that transfers any account that is 60 days past the "Last Touch Date", which is a formula field. The "Last Touch Date" field takes the most recent date out of the Last Activity Date, the Created Date, and the Last Transfer Date.
The problem? Even if the Last Touch Date is updated, the time-based workflow still fires when it originally planned. It doesn't get pushed back.
Here is an example. Take a look at the John Lewis record in the queue, which is scheduled to fire in two days:
Now look at the Last Touch Date for that John Lewis account, which was updated last week (therefore the time-based workflow shouldn't fire until another two months):
And here is a screenshot of the workflow rule:
Any idea why that would happen? Am I understanding time-based workflows incorrectly? Any help would be much appreciated!
Thanks,
Greg
10 answers
Hey Ryan,
I see that I can make a trigger on either 'Tasks' or 'Events', but obviously I want both to update the account when they're created. Do I have to make two triggers? One for each?
Thanks!
-Greg
