If you are deploying new package or updated custom packages and it has new dependent packages, you have to deploy the dependent packages too in the autodeploy folder. If you are deploying a new package or updated custom packages with existing dependent packages that are already deployed, then Microservices Runtime activates the new package. If you are deploying a new or updated custom packages with missing package dependencies the activation will fail. Also, if you are using hot deployment then you should identify package dependencies correctly. For more information see webMethods Integration Server Administrator’s Guide.