Best practice for trigger a process definition after a long period of time.

Hello, I hope you are all well. I have a request from my business to update a field on the contact record after 120 days, simple enough, so I thought. My first thought was to create a Process Definition to look for the event and wait 120 days. But I had some thoughts that I wanted to get feedback on. 

  • Does having several process in a waiting status cause issues? 
  • How long can I reliable keep a process in queue? 
  • What is the best practice for queuing PD's after a long period of time? 

I did some searching around but couldn't seem to answer these. Words from your bright minds will be greatly appreciated. 

Parents Reply Children
  • I'm not aware of how specifically the workflow maintains long processes run - that only developers know, but in general, the "hibernation" of the generic process instance increases the risks of technical failure at times.
    Therefore, I'd suggest just setting a-day-to-return in the database (versus relying of probably temporary storage) and set up a generic daily process of filtering the records to review on the basis of a-date-to-return

    This approach is employed by Need To Do Viewer addon for managing dates not-to-miss: integroscrm.com/.../

    Best Regards,
    Dmytro Chupylka

    integroscrm.com
    We make work in Sugar CRM system faster, more convenient and efficient