Good day,
I couldn't find an existing discussion about this. Since I updated the pac cli to 1.9.8 (most recent version) when pushing the pcf to any environment it mostly fails due to an allegedly running publish all but I'm even deploying to test environments and it doesn't work either. This morning tried it again, push failed. I have a gut feeling that this might be because of updating the pac cli. Will test this morning and report back.
How do you tackle this issue? Did any of you experience the same error when there shouldn't be a running publish all? Does anyone know if I can check if a publish all is still running beside solution history?
Hi Diana, thank you very much. Timeout increase for pac is exactly what I was looking for without telling.
Hi @Anonymous ,
@ScottDurow wrote a blog about increasing the timeout for pac: https://develop1.net/public/post/2021/05/19/increase-timeout-for-pac-pcf-push
If you use the Power Platform VSCode extension, you find the way to do the same in my blog: https://dianabirkelbach.wordpress.com/2021/06/24/troubleshooting-power-platform-extension-for-vscode-pac-connection-timeout-co/
Hope this helps!
Yes, I realized the async job takes that long that the connection times out and the cli says it couldn't be published. In most cases it was published and only showing errors in the cli!
I have seen no such issue with PAC 1.9.8:
Are you sure you don't have other people in the environment making customizations and publishing? A Publish All also happens during solution imports and as part of pac pcf push and other operations.
WarrenBelz
146,745
Most Valuable Professional
RandyHayes
76,287
Super User 2024 Season 1
Pstork1
66,091
Most Valuable Professional