This stems from REPO-587 too but again is a more general problem. When a deployment fails for whatever reason (missing dependency, failure to download some artifact, etc.), you can end up with half-installed features. For example, we had the osgi main bundle deployed, but the dependency bundle not deployed. Removing the app from the deployment profile doesn't cleanly undeploy, so we're left with the agent in a semi-deployed state. Quite often I have had to just delete the data directory in servicemix 4 to make sure i was back to a clean scenario. To see this error in action 1) Start up your repo 2) Start up SMX3 with an agent installed 3) Add the logisiticx demo 4) Add the relevant apps to the default portfolio and publish 5) You will see that SMX3 will try to add the relevant bundles - but SMX3 isn't compatible with these bundles and so it is only partially deployed , the user isn't notifyied of this error 6) There is no way to get rid of these deployed artifacts other then cleaning out the data and the relevant bundles in the deploy folder