Actually I realized my problem was due to using an incorrect column name. The column name was valid from a syntax and contextual respect but logically was incorrect as I was using the column name from the wrong data source within the expression.
The result was that although the Report ran, no data was set to process so the report did nothing.
The problematic part is that when I attempted to access the log entries of the Report run, the system wouldn’t show anything. If it would have, maybe it would have clued me in that no rows had been selected to process on the Report?
I’m not sure why the log entries would not show. I’ll try it again today to see if the same issue occurs and if so, open a bug on it.