Some time ago we had a an issue where one of our teams had a deployment failure due to the service fetch task timing out. According to Harness support, the fetch depth for the Harness CD service fetch task is 50. For large repositories this fetch depth can be potentially problematic. In these cases it would be preferable if we could configure the fetch depth or the timeout on the service fetch task.