This happens from time to time, and in my experience you will need to re-build or re-load the rule from a previous backup when it still worked. It seems to be less often now than it use to but it can still happen.
In future if you are going to edit a rule it's best to clone it before you start, in case this happens, especially on a large rule. It's an extra step but it's worth it when these type error occurs.
Based on the error you shared, this might be related to the driver you are using, and not so much with the app itself. If you are using a custom driver, that might be the problem.