Jobs fired by Event fire again the next day even if not scheduled

[MichaelB]

Good morning Cognoisosians (is that a real word)!

So I am hunting down something that I have been unable to Google or see anything related to it in IBM's Fix lists. Essentially what is happening is that jobs that run off of an event seem to fire again the next day even when they aren't supposed to. Let me break down our process and a few examples to clarify.

We had an Event Agent set up that listens for a trigger that is sent daily once our overnight data warehouse batch process is complete. The Event receives the trigger and process the criteria, which at this point checks to see if the _day_of_the_week is in (1,2,3,4,5) (M-F) and that our membership count is > 0 (because it needs some actual data to run). This all happens perfectly fine and if the criteria is met, it fires the M-F Job.

The problem that we noticed was that the job was running on Saturdays as well. It might be a simple thing where the beginning of the week was improperly defined you say, however, not only is it set correctly but the job runs 6 out of the 7 days as opposed to 5 out of 7 like we would expect if the first day of the week was shifted.

Then I noticed for the jobs that we have set for Monday or Tuesday only, the jobs were running Monday and Tuesday, or Tuesday and Wednesday. Always the day that they are scheduled, plus an extra day tacked on to the end.

Has anyone come across this issue or is aware of a fix that takes care of this? I wish I could say we were on the latest release, but because of priorities we are still on 11.0.0.

Thanks in advance for the help!