The timeout (in minutes) of Advanced clone or checkout behaviours under the configuration of either multibranch or the standard pipeline was not honored and remained at 10 minutes. 

The remote git repo is on Azure DevOps if it makes any difference

So during the multibranch pipeline setup, it always failed during scan with a timeout after 10 minutes instead of the 60 minutes intended

If I put the timeout inside the pipeline checkout step, it is then honored.

 
               checkout([
                    $class: 'GitSCM',
                    branches: [[name: '*/main']], // Adjust branch as needed
                    userRemoteConfigs: [[
                        url: 'https://XXXXXX/REPHGEN_AI/_git/REPHGEN_AI',
                        credentialsId: 'XXXXXXX' // Your credential ID
                    ]],
                    extensions: [[
                        $class: 'CloneOption',
                        timeout: 60, // 60-minute timeout
                        shallow: true, // Shallow clone
                        depth: 1, // Minimal history
                        noTags: true // Skip tags
                    ]]
                ])
 Then from the job output, the 60 minutes is effective afterward 

14:17:12   > git fetch --no-tags --force --progress --depth=1 – https://XXXXXX/REPHGEN_AI/_git/REPHGEN_AI +refs/heads/:refs/remotes/origin/ # timeout=60
14:17:15  Checking out Revision ee864f72aa07e3bf29be90097f5d465e1c547a6b (refs/remotes/origin/5683-AWSInfra)
14:17:15  Commit message: "Updated deploy.pipeline update branch"