Non-fulfilled routes appear as solution

[jie31best]

one possible reason: the hard constraints control the insertion phase, but the ruin phase could break them.

like what we discussed in one of your earlier posts:

HardActivityConstraint behavior

Is it possible that a route (list of activities) which fails HardActivityConstraint be part of the final response? I’m currently am experiencing this issue and would like to know if it’s my dab or the library’s. I’ve made sure every time a route with an specific list of activities goes through a certain constraint it fails, even singled out the shape of it. But it continues to appear. The other case are routes which never pass by the constraints end up being part of the result.