A Jenkins library update lands and one controller keeps loading the old Groovy code

Only one Jenkins controller keeps executing old library logic after a shared library update.