I noticed a timeout bug when you have no solutions to deploy and you want to purely released data packages. This is an edge case scenario but someone else might encounter it
Example
<?xml version="1.0" encoding="utf-16"?>
<!--
More information about ImportConfig.xml file
https://docs.microsoft.com/en-us/power-platform/alm/package-deployer-tool
-->
<configdatastorage xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
installsampledata="false"
waitforsampledatatoinstall="true"
agentdesktopzipfile=""
agentdesktopexename=""
crmmigdataimportfile="">
<!-- solutions to import -->
<solutions>
</solutions>
<templateconfig>
<dataimports>
<dataimport datafolderpath="data/servicebusconfig/extract" importconfigpath="data/servicebusconfig/ServiceBusConfigImport.json"/>
<dataimport datafolderpath="data/services/Extract" importconfigpath="data/services/schema/importconfig.json.json"/>
</dataimports>
<sdksteps>
</sdksteps>
<processes>
</processes>
</templateconfig>
<filesmapstoimport>
<!--
<configimportmapfile filename="FileMap.xml" />
<configimportmapfile filename="ZipFileMap.xml" />
-->
</filesmapstoimport>
</configdatastorage>
Example hanging pipeline

I noticed a timeout bug when you have no solutions to deploy and you want to purely released data packages. This is an edge case scenario but someone else might encounter it
Example
Example hanging pipeline
