What's happened is your QRecall scheduler wasn't running until you started up the QRecall application again. As soon as you started the QRecall application it realized this and started the scheduler, which took off and started running all of the past-due actions.
Why it wasn't running and how it was installed is dependent on a number of variables: what OS you're running, how your preferences are configured, and so on.
So rather than play twenty questions, the easiest way to diagnose this would be for you to send me your log files. The log files are in your <home folder>/Library/Logs/QRecall folder. Create an archive of the QRecall folder and either e-mail it directly to
me or upload it to the forum. These should paint a clearer picture of what's going on.