Hello, could it be that there is a small mistake in the changelog? Take a look at the exception when no record is not found part on the new findUniqueOrThrow function very at the ending.

Hey there! Could you be more specific about what the mistake might be?

@luwol03 it’s no mistake in the changelog ref they are deprecating

rejectOnNotFound

(but it still works in version 4.0.0) so it can be more explicit. Matt makes a good case to it. But in most cases you shouldn’t need it unless you want to be specific in your error thrown for a certain case you want to deliberately throw an error on the BE but not show on the FE. Thats what I gather but I could be wrong 🤷‍♂️