Mendix introduced the "Mendix studio target”, in the V4 you can set one environment to be the studio target. When using "Deploy to Licensed Cloud Node”, it will also move the package to this environment and restart it. For the V3 there were some issues, but they should be resolved now.
When creating packages locally, be sure to have the correct JDK present and selected in the project settings. You could try to build a package in the cloud, by using the button "Create package from teamserver” in the environment settings of your project.
See this forum post: https://forum.mendix.com/link/questions/102390 It is a new feature from Mendix that has not been thought through and is very confusing. This should be changed because it is causing a lot of confusement and frustration.
Does this action worked before?
Alternatively, if oyu have a lincenced node, you could build the package based on the latest revision and deploy it then in the sprintr
Dangerous setting. When you have to put a hotfix in production and it should not to deploy in acceptance (when target is acceptance), now it always put your hotfix into acceptance first. This is not always desirable.