Answer
First confirm you're actually completing the print action — the rule fires off the print event itself, so it only evaluates after pressing OK/confirming on the print dialog, not just from opening it. Check the Report Rule's own log next: a 'No condition met' (or similarly worded) log entry there confirms the rule is being evaluated but its condition isn't matching, which narrows the problem to the condition logic rather than the rule's trigger wiring. To isolate further, temporarily remove the condition entirely and confirm the rule fires unconditionally on every print — if it does, the issue is specifically in how the condition is written; if it still doesn't fire even unconditionally, the problem is with how the rule itself is wired to the report/action rather than its condition.