Asteroid-searching contracts requiring wrong orbit for Sentinel!?

[Neilski]

(v1.9.1)

I currently have two asteroid-finding contracts. One is for Eve and the other is for Kerbin.

While checking today if my Eve Sentinel was happy with its orbit, I looked more closely at the contract orbit requirements and was puzzled to see that the orbit is ABOVE Eve - I looked at it in map mode and it's outside Eve's orbit at all points. I then checked the Kerbin contract and it's even more perverse - it's all the way out near Duna (semi-major axis in the SFS file for that one is 19.05 Gm).

Just for the hell of it, I sent a Sentinel out to match the Kerbin contract requirements and sure enough the Sentinel now says it's mapping Duna. When I warped heavily I was seeing some asteroids detected for that contract but then I realised I still had another valid Kerbin-mapping Sentinel active, and when I switched it off and warped for hundreds more days, not a single Kerbin asteroid was matched to the contract.

So I guess this is a (fresh?) bug. Anyone able to confirm?

I've posted in the modded section because I use KAC. It's up to date as far as I can see (3.12.0.0) but this doesn't really feel like it can be a mod-induced problem anyway, given that the contract itself is fundamentally broken.

Edit: it might be relevant that during the long high-speed warps, I saw an error flash up in the top right corner of my screen a few times - orange text, saying "[ContractSystem]: Attempted to generate contract with no celestial bodies available." I have no clue how to interpret this but it doesn't look healthy.

Edited March 1, 2020 by Neilski
addendum

[Cavscout74]

I've encountered that in 1.8.1, most of the Kerbin orbits are well beyond Kerbin and the Eve contracts are requiring orbits closer to what were previously Kerbin contracts.