That's it! I changed the compatilitylevel of the database because I needed to use some function (can't remember what), but I changed the server to 150 (2019). I overwrote the database and ran all updates (including the compatibility level) but on the "new" database the issue doesn't yet exist