Same here (I guess ... if that's what you meant):
The JOBS in the scheduler says "Ready for generation", while the JOBS with the exact same RunID is ENDED_OK. I assume this is a simple logic/display issue where the JSCH monitor shows the previous run id, but the state of the next upcoming job instance.
Automic Web Interface 12.1.1.HF3-dev-feature-12.1.1-HF.3-70410
Automation Engine API 12.1.1+build.9812
Best regards,
Carsten