Custom route always 404

<@604068445499162664> I have found the solution, which is a weird behaviour:

The routes are loaded for each file located in /routes for a particular object, in an alphabetical order. My order is: