I am getting Transport Failed error while deploying the package to mendix cloud(acceptance)

0
Getting below error while deploying the latest package to Acceptance instance. An unexpected error occured: Transport Failed. Please try again and contact support if the problem persists Can someone help me if you gone through this issue earlier. Following are the some points for you to understand the issue better 1. Only the deployment package created by me is not being deployed. But the package created by other developer earlier, it is deploying successfully. 2. We both are using the same branch to commit and to create package as well. 3. This is the first time, I have committed and trying to deploy. 4. The only difference from both the packages is that the difference in size of package, mine is having 230MB where as earlier successfully package having 203MB size even though I have only a small condition in a microflow.
asked
4 answers
1

Unfortunately we can't see what's going on in the background and there are no issues reported on https://status.mendix.com/ . I would recommend opening a ticket with Mendix support.

answered
0

Hi Pawan,

I faced a similar issue last month. I was trying to deploy my App on Cloud and repeatedly, I was getting similar message. I closed all my Apps and Studio Pro, logged off from Studio as well as other portals like Forums and Academy etc. I still had a Mendix Studio process running in the background in windows( could see via task manager), I had to manually kill it.  I closed all my browser windows also. After that, I  opened everything again and  it worked fine.

I am not sure, if this happens due to some hanging processes in the background or what, but, its worth a try. Otherwise, anyways, you will need to open a ticket with Mendix Support

Regards.

Shekhar

answered
0

Data folder size is huge. Removed few data. Now deployment package is having size less than 1GB and able to deploy it in acceptance instance.

Thanks

answered
0

Your deployment package is probably too large as others have suggested. This issue usually occurs for me when there is a data snapshot present in the deployment package, as a data snapshot can easily be double the size of your actual project or more. Check to see if a data snapshot is present in the root file of the explorer and remove it before creating a new deployment package( IMO this is also just a general best practice ). I usually just keep a recent snapshot handy elsewhere on my computer just in case it’s needed for one reason or another. 

answered