We've got the thinBackup plugin running regularly (see settings in attached screenshot).

Lately a pipeline job has been created that runs nigtly. The job has kind of the following pipeline script:

node {
    stage('master') { // for display purposes
        build job: 'JOB_NAME', parameters: [string(name: 'BRANCH_OR_TAG', value: 'master')], propagate: false, quietPeriod: 1
    }
    stage('branch1') { // for display purposes
        build job: 'JOB_NAME', parameters: [string(name: 'BRANCH_OR_TAG', value: 'blub1')], propagate: false, quietPeriod: 1
    }
    stage('branch2') { // for display purposes
        build job: 'JOB_NAME', parameters: [string(name: 'BRANCH_OR_TAG', value: 'blub2')], propagate: false, quietPeriod: 1
    }
}

Problem is that the backup process seems to start in the midst of the pipeline build. While the pipeline build is waiting for the next build of a defined job, Jenkins is in quietMode and won't continue to build. So the pipeline job "hangs" and the backup will not be done until manual interaction.

Maybe the thinBackup plugin could offer a setting to decide on how to handle these situations. Only option that comes to my mind currently is to automatically abort the affected pipeline jobs.