When you change a field value, sometimes the timestamp in the Frappe database does not get updated. Because of this, the message appears. You need to refresh the page first, then enter the values again after that, the issue will not occur.
Thanks for the suggestion, but this is happening during a Data Import job — not from manually editing a form. The timestamp conflict occurs entirely within the import process itself, with no human interaction involved.
You can see this in the timestamps:
• 22:07:14 — importer opens the document
• 22:14:01 — importer tries to save it
That’s a 7-minute gap caused by the importer’s own internal writes racing against each other. Refreshing the page doesn’t apply here.
This is also happening across multiple sites immediately after upgrading to v15.101.3, which points to a regression in the Data Import background job logic rather than a UI/session issue.
Got it, thanks for the clarification. Since this is happening within the Data Import job itself and across multiple sites post v15.101.3 upgrade, it does look like a regression in the background import process rather than a user/session issue. The 7-minute gap clearly indicates internal write conflicts. This likely needs a fix at the framework level.
I have managed to sort the issue by migration to version erpnext 15.102…
and frappe version 15.103.0
Good.