Problem with table data revert

[Claudio Casanovi]

Hello everyone

we have an Asp.NET project that is based on an old version of nhibernate 4.1.2 due to the target framework 4.5.2 on Windows Server 2019 and SQL Server 2019.

Around 20 people work on the product at the same time.
We have had 3 episodes in the last year of "data reverts" on a table hours after the last edit actually committed to the database.

The rollback happened only on one table, the most stressed (the others don't have).

After these events we proceeded to migrate to the new target framework and update nhibernate to the latest release, but we would like to know if you have any idea what might have happened.

It doesn't seem like a SQL Server problem, but rather as if an nHibernate session had written a previous state to the database.

I know it's not easy to answer with so little information on a complex problem, but could be a bug from an old version or rather an implementation problem such as incorrect use of sessions?