PubSub for job runs, so the Jobs page follows a run as it moves instead of polling. Two topics: topic/0 hears every run, run_topic/1 one run. A message is {:job_run, action, run}, where action is what happened (:started, :progress, :paused, :completed, …).

Always published after the transaction that made the change has committed, so a subscriber never hears of a change that rolled back (PhoenixKit.Jobs.Engine).