After checking the WinGet submission, it appears that the Azure CI pipeline associated with winget-pkgs is timing out because the tablecloth program is auto-installed immediately after the package installation.
What to look for
Need to test to make sure that the program does not autorun after installing the package with winget
Consider removing the option to autorun after the installer completes, as this behavior was not present when deploying as a traditional MSI package
I needed to prevent the program from starting automatically when using the unattended installation option, so I made sure that it didn't start once the installation was complete.
After checking the WinGet submission, it appears that the Azure CI pipeline associated with winget-pkgs is timing out because the tablecloth program is auto-installed immediately after the package installation.
What to look for
Related Report: https://github.com/microsoft/winget-pkgs/pull/138227#issuecomment-1932463697