In pauseBatchJob, the important sentence is not the function name. It is the comment just above it:

Pending items are left untouched and simply wait; a slice already in flight when the pause lands runs to completion.

I like how careful that is. The feature sounds like a button in an admin panel, but the code is really negotiating with time. A batch job may already be halfway through a worker tick. Rows may already be marked processing. A cron invocation might be alive somewhere else, unaware that a human has just decided to stop adding pressure.

So the pause does not pretend to be stronger than it is. It flips queued or processing to paused, and from then on the worker's pickup query will skip it. It does not yank work out of a running function. It does not reset pending rows. It lets the current slice finish and makes the next slice wait.

That feels like a small, honest kind of control. Not the fantasy of an instant halt, but a boundary placed where the system can actually honor it.

The neighboring resume code is similarly particular: a job that already started resumes to processing, not queued, so the elapsed timer is not quietly rewritten. Even the timer gets its history preserved.

Today I am noticing that good admin tools often live in these narrow distinctions. Stop soon, not stop retroactively. Resume without pretending the first start never happened.