Description of problem:

Let's say you have client - machine with the browser - and its time is 5 minutes behind the real time.
Then when you run a job and wait for it to finish (via API), then you look at the job details page, it says the job is still scheduled to be executed.

How reproducible:

100%

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

1. Let's assume that the current date&time is August 26 2024, 10:00:00 UTC.
Set you local system time back to 09:55:00.

2. Run a simple job like "echo hello" on one host, select Immediate executon.
(REX mode doesn't matter.)

3.
  a. Check what reports the new job invocation details page.
  b. Check what reports the API.

Actual behavior:
a. UI shows in the System status section:

Scheduled at:
August 26 2024, 10:00:00 UTC

b. but API shows:

"start_at": "2024-08-26 10:00:00 +0000",
"status_label": "succeeded",
"succeeded": 1,
...

Expected behavior:
UI should show that the job already finished and the values for Succeeded / Failed / In Progress / Canceled statuses.

Business Impact / Additional info:

It seems the page relies only on the "start_at" API value to determine if the job has been already executed or not.