This seems to be an issue with one of the more recent versions of nextjs. I reverted from 15.4.1 to 15.3.5 and it works as expected again.

Annoying that this is a larger released bug that should have 100% been caught in testing, but a revert to the previous version should fix.