Comment 1 for bug 2031931

--force is an option of last resort to be used in specific circumstances, and may have rough edges. It's supposed to only be used in situations where normal app removal cannot complete due to things like cloud resources being removed out of band or other similar scenarios. Is the use case here one of those scenarios? We strongly recommend not using --force as part of normal operating procedure, because things need to be removed and cleaned up in an orderly manor.

Having said that, if there's a model artefact left behind when using --force, that is something that should be fixed. Can you share what charm / cloud / storage is involved and anything else to allow the issue to be reproduced?