Jenkins needs to know a PR exists in order to build it. There are many
reasons why this information might not reach Jenkins, e.g. GitHub might
have failed to send the webhook, or there was a network error somewhere,
or Jenkins was down at the time, or (most likely) the GitHub API rate
limit for
ci.jenkins.io had been exceeded at the time.
You can see in the logs that Jenkins indeed failed to scan the repo due
to being rate limited:
https://ci.jenkins.io/job/zap-plugin/indexing/events
However, a build of that PR has since happened, so presumably the "poll
periodically" option of the multibranch project kicked in (at a time
when the rate limit hadn't been exceeded).
Regards,
Chris