This is still present in 4.20.2, but thank you for the workaround, guys.
Edit: A safer way to work around this might be to create a normal function (e.g. “notify_VariableName”) taking the repNotify variable as an input in the parent class, calling that function in the parent’s Notify and passing the new value, then overriding/extending the new “notify_VariableName” function in the child class.