[ https://issues.jboss.org/browse/WFLY-5474?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-5474: ---------------------------------------- This almost certainly is not a critical bug. You need to choose how you want to manage your deployment -- via the scanner or manually via the CLI. Switching from one to the other is something where we try our best to let the scanner figure out what you've done manually and keep up, but it's really a best effort. If you are using the scanner for your deployment, stick to the scanner. I suspect what happens here is the deployment is still owned by the scanner, since :undeploy / : deploy doesn't remove/re-add the deployment. Then the scanner's attempts to track what happens with the deployment get lost after the :undeploy. The effect is when you reload, the deployment is owned by the scanner but the scanner considers it undeployed and doesn't deploy it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)