The previous version of the macro acted on the currently selected tasks and got confused if you changed the selected task while it was running. That problem has been mostly addressed now although you can still confuse it if you change the selection just as it is calling the ResultsManager set-task-complete macro.
While testing this bug fix this evening, I noticed that my "completedlog" map was missing a lot of my history and uncovered a larger bug in the way that the macro was creatign the completedlog.mmap initially.
On Error GoTo X
If Err.Number>0 Then
The program would try to open the map, and if it encountered an error, it assumed the file didn't exist and created a new one. The problem is that if it experienced an unrelated error at this stage, it would overwrite the existing map.
In retrospect, this was a sloppy way to handle the initial file creation, but it seemed to work OK in the early days when the entire program was just a line of code in a small GyroQ tag. My guess is that v7 gives occasional file errors that didn't occur in v6.
If you are using the program, please update to this latest version ASAP and check your CompletedLog to see how far back it has data.
I recommend retaining your completed items in your maps in addition to the completedlog. I keep mine in a floating topic called "completed" so that they don't clutter the main branches. I also highly recommend setting up your computer with backup software to do nightly backups onto a USB drive with version retention.