When a kogito decision application using the tracing-addon starts it emits ModelEvent(s) holding the definition(s) of the models deployed. This event leads to the model definition being persisted.

When a hot-reload is triggered the kogito application is re-deployed and the ModelEvents emitted again. However the persistent store (PostgreSQL in DevMode) is not re-started and the database content persists over the re-start. This leads to a warning being logged that the model is already present in storage.