Okay this has been an ongoing issue in TSW for a long time. If you finish a service, return to free roam and take over the next working (or move to another train) when you save and reload the run the objective data and the clock fail to load. Just happened again to me on SF Corridor. Had Quick Play generate an ECS move from the sidings into San Jose Diridion (273F). Returned to frre roam after it completed, changed ends and took over the next service (273 to San Francisco). Just went to load the save and the usual problem manifested - you cannot proceed further as the objective data has not loaded. This seems to have fallen into a black hole as regards resolution. However a bit of investigation does reveal a possible cause, that the Load screen on the menu still shows as being the first train 273F, not Train 273. So maybe the game is not correctly saving the objective data in the first place (rather than being a loading issue) as it still thinks you are on the original working. Just a thought.
It appears that some aspects of the UI’s normal behaviour doesn’t update when chaining services in timetable mode. The debrief screen at the end of each service isn’t correctly labelled and if you pause the second, third or further service and select Restart it restarts the first service instead of the current one. I think the actual services you play after returning to free roam must be separate from what the game remembers about how you started and that impacts many aspects of the UI and saves etc.
H'mmm sounds like it might be a more fundamental issue than just the save/load itself. A shame really as it precludes running a complete shift and seeing how delays etc. could mount up and influence the outcome of subsequent trips.
