I have a requirement to send out reminders via email a certain # of days prior to two independent dates (call them R1 and R2). R1 and R2 set in a workflow which is trigger upon list modification. R1 and R2 can change during the day - so I can't just do a reminder workflow with a pause until. R1 and R2 might move up or down in dates.
So set a field called h-earliest-reminder (set via a workflow) which is the earlier of the two (or blank if they are in the past or blank themselves).
I put in a info management policy to run a workflow called Reminder based on the h-earliest-reminder date - I also set recurrence of 1 day in the info management policy rule.
(If you don't set recurrence, and it has previously run the workflow - it won't run again I've learned)
Everything works in testing during the day.
The problem is that the Reminder workflow is triggered sometimes when the h-earliest-reminder date is blank by the info M policy! In another case, the h-earliest-reminder set to 2/9/2018 yet the reminder WF was run on 2/8/2018 (policy should have waited until 2/9/2018 to run it). In another case, the reminder workflow wasn't triggered at all by the policy where others with the same reminder date were triggered... Why does it not trigger all records with the same date?
Right now, I'm changing the reminder workflow so that it checks to see if it was properly triggered and only send out notifications if it should be running. I was hoping info management policy would trigger it properly but that doesn't seem to be the case.
Anyone ever set up a reminder WF- which must be based on a reminder date field which can change?
There are about 2000 records in this list - I don't want to run a workflow on every record every night to check on reminders
Another interesting feature: the reminder WF modifies the record sometimes - one feature is that this does NOT trigger another workflow which is set to trigger upon modification.
Environment: SP 2013 on-premises with SP 2010 workflows ONLY - no Ninex or other extensions - Full control only (no SCA, no access to central admin, etc)
I've double checked with the farm admins and the timer jobs seem to be running properly every night - no other developers complaining about problems.
I make sure to reset the policy workflow whenever it is changed (you must refresh the policy or it will run the old workflow version)
The Info policy timer jobs run overnight about 2am, every day. This cannot be changed.