I'm not aware of any specific mention of this issue, though it's possible it could be related to one of the known Rule trigger issues:
Either way, your rule in its entirety and the output from Logs with all logging enabled would be necessary to both demonstrate the problem and assist with troubleshooting if it's a Rule 5.1 problem.