Ecto error triggers HTTP 404 instead of 500

An Ecto (no results) error raised inside a Phoenix controller triggers a HTTP 404 response, instead of 500. I am currently on Phoenix v1.6.2, and pretty sure that this was not the case previously. Any ideas as to why this might be happening, or how it could be dealt with?

It was the case when you have phoenix_ecto library installed.

1 Like

Thanks, I was puzzled as to where that 404 was coming from.