Hmmm weird John. Ok did some more tracking, appears that "tour" leg 8 pirep never was submitted so the system won't give you tour leg 9. Now you did fly the single flight MFCT00011-6A0 LLWS to HYL but that won't trigger leg 9 inside tour 2.
So what you have to do is trigger tour 2 leg 8 details again, generate a bid then because you have already flown the single flight leg (MFCT00011-6A0 LLWS to HYL), just pop in a manual pirep for that tour 2 leg 8, and then that will trigger leg 9 to become available for you.
This tour module contains it's own embedded legs and they are generated via the bid method steps only. KAcars directly loads these generated bids in (with the setting search by flight number UNCHECKED), by the single click of the "Get Fllght Data") (after the tour bid has been generated.).
Now to perhaps to clarify for all: A single flight leg is not a tour flight leg. (I have built single flight legs (that are the same as embedded tour fights only so that these routes or flights legs can be flown outside a tour as single flights BUT they don't replace and do no substitute in the system as a replacement for the embedded tour legs and they can't generate the next leg of a tour - because the are not associated to a tour at all. If this makes any sense.
So all to say we have single flights - and they can be flown at any time but have no relevance to a tour.
The tours. Their embedded flight legs are only contained or generated from inside a tour and are only flown once and contribute to that said tour as being a part of that tour and the following leg will not become available until the previous leg has been completed.
Clear as mud?
Norm