I want to use The Bat to queue up a large amount of messages to be sent out over time, but I cannot keep the software running at all times (there are daily messages for over a year!). I have created a number of test messages and set them up with a custom delivery time.  If the scheduled event happens while The Bat is still running, there is no problem and the message are released from the queue as expected.

However, if the software closes for any reason the messages get stuck in queue.  Each of the messages has the "Execute actions for missed events" box checked as well as the "Notify about missed events on startup" box.

The problem is that at startup the program does not seem to recognize the missed events so there are no notifications and because the time has already passed for the queued message the time never arrives to trigger release from the queue, hence they get stuck.

Is this a configuration error on my part (in which case I would like to know what I have to tweak) or is this a software bug?  I am using the 5.0.14 release so I should be up-to-date.