Suddenly having the above error at two different clients. any new information on this error? It appears when running an April 2023 report *only* where it hadn't appeared in the past. Same for January 2023 *only* for the other client.