-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment to the sandbox environment failed with the error message: "underlying connection was closed." #1086
Comments
could you include timestamps in the dump? |
|
@freddydk The timestamp in the dump is noted above. Additionally, the Business Central extension isn't providing any insights. The issue stems from the previously installed extension being uninstalled after a deployment failure, which is causing access problems for the user. Although rerunning the CI/CD pipeline sometimes resolves the deployment issue after 2-3 attempts, we need a solution to prevent deployment failures caused by the "underlying connection was closed" error. Thanks for your assistance. |
Any update on this issue? |
Sorry for the delay here |
Sure. It fail 4 times to deploy a merged commit. But the strange part is that after like the 3-4 times of failing, we get the failure error that says |
Is there a way to increase the timeout, it seems that the app is still deploying but it time out early with an error @freddydk |
Hi team,
I'm deploying to the sandbox environment and have noticed that the first deployment attempt often fails with the error message "underlying connection was closed." Unfortunately, this issue causes the pipeline to uninstall the existing extension in the environment.
Can anyone explain why this error occurs? Also, is it possible to configure the system to reinstall the previous extension or automatically relaunch the pipeline whenever a deployment fails?
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: