Sure, if can come up with a pull request, I’ll gladly peer review it.

Regards,

Carlos Ruiz

Thanks Yes that is what suggested (checking the existence of the record before the update.). we tried to find solution, but cant get it work. Would be reasonable to fix this error.

We have many logs daily minimally 20-30 use cases. then struggling is this real error, mainly where node CPU is being too high (standard avg 10% in such cases climb to 50-70% - not sure caused by this but in 99% this type of log exists when alarm hit treshold. )

norbert

Hi - this message is caused by the fix in

When completing multiple documents sometimes there is a chain of transactions, when one of the “child” documents fail, the transaction is rolled back, but still the “parent” document tries to update activity and event audit and fails (because it was rolled back) - writing that message in the logs.

I could be wrong, but from what I understand the message is harmless. Maybe it can be improved to be managed better, like checking the existence of the record before the update.

Regards,

Carlos Ruiz

same here

https://test.idempiere.org/idempiereMonitor?Trace=/opt/idempiere-server/log/idempiere_20210118174438.log

https://test.idempiere.org/idempiereMonitor?Trace=/opt/idempiere-server/log/idempiere.2021-02-11_0.log