Event Listener should not figure out time for sepull scripts to run

Right now the UserAccountService runs a timed service every 15 minutes. When a time zone in our system (tsacommon.timeZones) passes midnight, it sends an event to the Event Listener. The Event Listener then schedules sepull3.sh to run after 3 hours and 50 minutes, sepull147.sh to run after 4 hours and 30 minutes and sepull164.sh to run after 6 hours and 30 minutes.

When everything is running fine, this works like a charm.

But if the Event Listener isn't running properly for some reason and has to be restarted, there can be an issue.

Today the Event Listener wasn't running properly. I noticed it at 6:30am Eastern and restarted. It was backed up so it took some time but around 7am it got the 'newTimeZoneDay' message for the Eastern timezone and scheduled the sepull processes to run after the above-mentioned time. If I let this run without intervention, Google data wouldn't even start to be pulled until around 11:00am Eastern.

So this involves manual intervention.

===WORK AROUND===

Manually run the sepull processes.

Go into /var/local/tsa/eventlistener/schedules.txt and find the lines related to the timezone(s) that are affected and remove the lines. Then restart the Event Listener (preferably after it is all caught up). Note, on Event Listener restart it reads that file and will reschedule based on the parameters and timestamp in that file.

===SUGGESTION===

It makes sense to let the UAS send as part of the message, the time the sepull processes should be run. That way if the Event Listener is getting the messages late, it will run it immediately if enough time has passed.