
Hi all,
I've created a workflow that sends out email notifications upon assignment of events along with reminder emails to automatically go out at certain time intervals (using the timeout process in workflows).
The entity that I've created as a start date and time as well as a end date and time field both set to be timezone independent and includes date and time values.
The workflow that I've created sends an initial email upon creation or assignment of the entity record to a contact and then a nested timeout process is set to equal 2 minutes before the "Event Start Date and Time" (again is timezone independent).
The initial trigger for the workflow works in that upon assigning the record, it creates a email notification but upon inspection of the system job it looks like it's stuck in the timeout step even though I've set it to timeout 2 minutes before a Start date and time I've set close to my current time. Is there some nuances regarding timeout that is effected by the timezone independent nature of the system?
E.g. below is a screenshot of the system job process. Note I set the start date and time field to be 4pm on the day I was running the test and set it to timeout 2 minutes before which means I should of received a reminder email at around 3:58pm. As you can see by the screenshot and time at the bottom right hand corner. It's way past the designated start date and time and I still haven't received a reminder email.
Any help would be greatly appreciated
*This post is locked for comments
I have the same question (0)Hi all,
I found the problem to this. Even though the date and time field itself is set to timezone independent, the timeout process runs based on your local time. That means I'd have to adjust my timeout timing so that it factors my timezone.