Since state is not persistent, this attempt to handle resumed builds is unlikely to work: there will be a new UUID registered, and any service posting back to a URL obtained prior to the restart will just fail.

There are no functional tests, much less anything using RestartableJenkinsRule, which would be the natural way to reproduce this sort of issue.

BTW there are also open issues in GitHub which is confusing. One or the other source of issues should be disabled.