Had the same error. Updated Optimum from 1.15.0 to 1.16.0. Error fixed.
· Sign up or log in to comment