I stumbled on a situation where an "Infeasible route" exception is thrown in plan mode, but the only hard constraint passed in input is a service_after value for start step, so no matter the violation level, a route should be found.

The problem happens because the upper bound for the start step is actually lower than the lower bound in this check. This is usually the sign of too tight timing constraints but here there is no constraints on upper values.