Little bump because we run into the same issue, after upgrading from 4.22 to 4.24. We haven’t found a solution yet.