I can reproduce this issue, in situations where the web app is offline during the publication date/time. The publication mechanism will not "catch up" to events that (should have) triggered while app was offline.
My guess is that the quickest work around is to either configure the apppool to not shut down after X minutes of being idle, or ir the apppool config is out of your reach, set a ping service up.
We will investigate further.
My guess is that the quickest work around is to either configure the apppool to not shut down after X minutes of being idle, or ir the apppool config is out of your reach, set a ping service up.
We will investigate further.