If archive fails to deploy it ends up as not policed by deployment scanner.
If archive is removed from deployment directory, its not removed from server, this diverges from how successful are maintained.

Workaround:

• restart server
• /subsystem=deployment-scanner/scanner=default:write-attribute(name=runtime-failure-causes-rollback, value=true)

To reproduce,

• modify https://github.com/wildfly/quickstart/tree/main/kitchensink and change DS name in persistence.xml, without updating app(to reflect this singular change, essentially break it, so it fail on deploy).
• start server
• cp archive to standalone/deployments
• rm archive from standalone/deployments
• jboss-cli.sh -c
• deployment-info

Last command will show app still being deployed in server