Since version 270.vdb_c342a_178b_f, we have been experiencing the issue of builds not completing successfully when the job is triggered by a webhook.
We have not yet been able to determine the exact cause or the impact of the plugin on the build process, but we have noticed that the Jenkins job configuration is marked as changed.

The exact process - the status of the Bitbucket branch - does not change:
When the Jenkins job is started manually, the build works.
If the job is then triggered by a webhook, the build no longer works and the job configuration is marked as changed.
If the Jenkins job is then started manually, the build still does not work.
We then opened and saved the job configuration without making any changes.
If the Jenkins job is now started manually, the build works again.
We repeated the job that was triggered by the webhook - the build also worked.
As soon as the job is triggered again by a webhook, the build fails again and the job configuration has to be saved again without making any changes.

With version 263.v7f6ef03c9ef8, the build process works both manually and via a webhook-triggered job.