locked
Sharepoint 2007 Workflow Email sent out a Year Early RRS feed

  • Question

  •   Good Morning,

     I have two wokrlows that have sent out email a year before expected.  The start and end times are in May 2012, but notices went out  April 30, 2011 that  "YOUR PRODUCT HAS EXPIRED"

     

    Clearly from the dates below (worflow details included at end of this email), the earliest notice that the expiry date was approaching would be sent 12/28/2011.

     

    Can someone clue me in what's happened here?  Thanks.

     

     

    Start Time
        4/30/2012 8:00 AM
    End Time
        4/30/2012 8:00 AM
    Description
       
    yadda yadda yadda .... Current coverage dates are 5/1/2011 - 4/30/2012.
    All Day Event
         
    Recurrence
         
    Workspace
         
    4 Months Ahead Reminder Date
        12/28/2011 8:00 AM
    3 Months Ahead Reminder Date
        1/28/2012 8:00 AM
    2 Months Ahead Reminder Date
        2/28/2012 8:00 AM
    1 Month Ahead Reminder Date
        3/30/2012 8:00 AM
    **Expiration Date
        4/30/2012 8:00 AM
    Final Reminder Date
        5/31/2012 8:00 AM


    Rico Coco


    • Edited by Mike Walsh FIN Tuesday, May 3, 2011 11:27 AM trailing .... in Title removed. Clearly an attempt to attract attention to post. Do this again and see your posts deleted
    Monday, May 2, 2011 4:39 PM

Answers

  • Figured this one out -- a user edited the date on the two workflows that sent out Final Notices a year early, and the updates showed on screen, but the actual workflow schedule was not updated.

    It would seem the workflow must be manually shut off, the edits made, then the workflow  restarted for the schedule to actaully change.

    This is still a theory, but I found the edit dates and compared to another future workflow item that was set to expire on the same date that had been edited a couple of days earlier.

    The only difference was that workflow was off system wide and turned back on after the latter file was edited, so its schedule was actually updated ....

     

    Hopefully this resolves the issue ....

     

     

     

     

     


    Rico Coco
    • Marked as answer by Rico Coco Tuesday, May 3, 2011 7:10 PM
    Tuesday, May 3, 2011 7:10 PM

All replies

  • Can you post the steps of the workflow and the workflow history?
    Monday, May 2, 2011 7:47 PM
  • Hi Ed,

     

    The workflow steps are as follows:

    If 4 Months Ahead Reminder Date is greater than Today

    Pause until Renewal Reminders Calendar: 4 Months Ahead Reminder Data

    then set Variable: Recipients to Renewal Reminders Calendar: Reminder Recipient
    then Email Variable: Reicpients

     

    The history for April 30th is filled 42 entries that, minus all the GUIDS, looks like

     

    4/30/2011 8:00 AM Comment 0  0 Pausing complete       

    4/30/2011 8:00 AM Comment 0  0 Pausing for 571679.943495193 minutes   

     

    Any clues you can provide will be greatly appreciated.

    Thanks


    Rico Coco


    Monday, May 2, 2011 9:00 PM
  • Not sure what is going on.  Not sure why it is pausing for ~5 months on April 30th.  I would add steps to the workflow to log all the notification dates so that you can see what they actually are.  When you first launch the workflow do you see a pause for the correct duration (~360000 minutes)?
    Tuesday, May 3, 2011 3:45 PM
  • Figured this one out -- a user edited the date on the two workflows that sent out Final Notices a year early, and the updates showed on screen, but the actual workflow schedule was not updated.

    It would seem the workflow must be manually shut off, the edits made, then the workflow  restarted for the schedule to actaully change.

    This is still a theory, but I found the edit dates and compared to another future workflow item that was set to expire on the same date that had been edited a couple of days earlier.

    The only difference was that workflow was off system wide and turned back on after the latter file was edited, so its schedule was actually updated ....

     

    Hopefully this resolves the issue ....

     

     

     

     

     


    Rico Coco
    • Marked as answer by Rico Coco Tuesday, May 3, 2011 7:10 PM
    Tuesday, May 3, 2011 7:10 PM