As mentioned in the other ticket, this is likely caused by the jenkins security update that no longer deemed the old access tokens secure so they had to be revoked. This shouldn't happen often so we can just start by manually issuing a new token and updating the job config.