Gavin Faux

@RPanc As a workaround, exclude the Articulate custom routes from your finder, reference this [thread](https://github.com/Shazwazza/Articulate/issues/439#issuecomment-1905917945). Note that example routes to filter are not exact, it's still possible to get 404's...

@khraibani is your articulate instance an upgrade from a previous version? We see exactly the same issue/error on a site upgraded from v7 to v10 - we have disabled the...

@wvdweerd @Shazwazza I'm seeing similar locally, due to the previous PR #436 which changed route priority, it's now too high and being skipped allowing not found handlers to kick in....

Have seen same issue on a previous working 5.0.0 site, two root nodes, first node has domain / culture assigned, second node nothing assigned (container for content blocks and settings)....