almex/Raildelays

Find why SearchNextTrainProcessor does not provide any candidates

Closed this issue · 1 comments

Get this strange behaviour with train 517 on 20/08/2014

The answer is : because it's the last possible train. So it's normal and not a bug