Is there an issue with RM 5.1 in 2.3.4.117? @bcopeland @bravenel @bobbyD
You have an empty/ghost final condition ("(F)") in the AND sequence. Edit the condition and delete that ghost - it will get fixed.
1 Like
Cheers, I hadn’t noticed that.
The weird thing is that this rule has been working fine until today and hasn’t been touched in many months.
This bug has been around a few releases. I haven't been able to reliably reproduce it so I can give a decent bug report. But, this has happened to me twice as well. What @minollo said is indeed the workaround.
2 Likes
Cheers, I thought I was going mad. 
1 Like
@bravenel This seems to be worse lately. There are a couple of threads with this issue. Sorry, I cannot give you a repeatable case. It seems to only happen with complex rules with multiple/nested IF statements. See this thread for info.
1 Like
I agree, you have to be very careful when you create complex IFs and keep and eye out for this. Like you, I can't quite come up with a scenario where it is repeatable but I have seen it quite often lately.
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
