I've had this happen several times recently with two ways of activating a macro. In each case I can tell that the macro hasn't run because nothing appears in the log file.
One macro is scheduled to run at 23.57 every day. It simply calls a batch file. For several days it didn't run at the required time. Then I changed the schedule to make it run about a minute after the change. It ran. I changed the schedule back to 23.57 and now it has run two days running at the correct time.
The other macro calls the Suspend script. It is activated by running MeProc.exe as a post-processing command from an Acronis True Image Home 2010 backup job. It was running successfully, but for the last two nights it hasn't run. I can tell from the Acronis log that the command to run MeProc was issued by Acronis, but the Macro Express log, which writes messages to the log file at the start and end of the macro, shows nothing, indicating that MeProc didn't run the macro.
Has anyone any ideas about why these macro activations should be so unreliable?