'Invalid field" errors on realtime DLRS

Hello all,

I am having a big issue with DLRS that I cannot uncover for a long time, and it's affecting my users big time.

We have several real-time calculations on our ticket object that started popping out errors, apparently on totally unrelated actions, i.e. actions when the rollup shouldn't run at all.

Basically we are running a calculation from EmailMessage to Case object, but for example, when we go to update a field on certain Cases, this DLRS supposedly triggers and tries to search for a field from the EmailMessage object on the Case? An error message is then thrown and I am basically unable to edit this Case. If I change the order of the Relationship Criteria Fields and put Incoming as the first field, I will get an error saying that Incoming is invalid on the Case object.

Obviously, these fields do not exist on the Case object, but why is the tool trying to find them there, instead of on the EmailMessage?

Mind you it's not all records on the Case object that we're unable to update, but I still haven't found a reason why some of these specific cases are failing.

Screen recording of the issue: https://www.loom.com/share/d6e17b870d734ac097ee8163ac85079c

I am a System Administrator in the org and I am added to both DLRS permission sets.

Even tried to recreate the rollup from scratch, no results.

The only solution so far has been to deactivate the rollup completely.

Seems to have started to happen when we upgraded DLRS to 2.15, but cannot say for sure.

If anyone has any idea about solving this or even troubleshooting further, please save me! Thanks!   #Declarative Lookup Rollup Summaries @Andrew Fawcett