When `saveEntity()` is called, it recomputes the `original_hash` from the entity currently stored in db and overwrites the value in the auto-save item. If the entity is of Canvas Page type with an unresolved conflict, such overwrite silently resolves the conflict without explicit user action as if `resolveConflict()` had been invoked and successfully executed. On the next call `AutoSaveManager::getUnresolvedConflictForEntity()` will return `NULL` potentially resulting in conflicting changes being overwritten, leading to data loss.