Two places show you a job while it's actually running, not just after it finishes.

Job Detail page: if the job you're looking at is running right now -- however it was started, this page's own Run Job button, the Jobs list, a schedule, or another Console -- a banner appears showing which server it's on, how long it's been running, and whether it's parked waiting on a Gate. Whichever step is currently executing is highlighted in the Steps list with a RUNNING badge; hover it for exactly when it started. The banner has its own Stop button (with a dropdown for Soft Stop -- finish the current step, then stop -- versus Hard Stop -- interrupt it right now) and its own refresh control, separate from the page's own data.

Current Runs report (Reports -> Current Runs): every job running anywhere in the fleet at once, filterable by server, with the same step-by-step timeline and Stop options for whichever run you select.

Both share the same refresh button (the small ⟳ icon you'll see in several places): left-click to refresh once, right-click to turn on auto-refresh and pick how often -- off by default, so nothing refreshes behind your back unless you ask it to.

While a job is running, its Run Job button (and the dropdown next to it) are disabled everywhere that job appears -- you can't start a second run of the same job on top of one already in progress. Trying anyway from outside the Console (the API directly, for instance) is rejected the same way.

Related: Gates -- one way a run ends up parked rather than actively running. Job Scheduling -- one of the ways a run can start without anyone clicking Run Job.

See also: Glossary for related terms.