I have a relatively long list of notifications and have run across a problem associated with using the “Set Property After Alert” feature. The issue is that I have multiple notifications (two in this case) both sending e-mail based upon conditions at the time of “Save”. Both notifications set a property after alert in the same doctype field. This results in only one of them setting the property because, apparently, two different notifications are attempting to update the same document at the same time.
I have a work around for this but it requires me to understand the order in which the notifications are processed. Chat GPTo tells me, with confidence, the following:
“In ERPNext, notifications are processed based on their creation date. This means that notifications created earlier will be processed before those created later. When a notification is modified, it retains its original creation date, ensuring the processing order remains consistent unless the notification is deleted and recreated.”
This sounds logical to me but I am unable to verify this is correct and, of course, don’t want to blindly believe Chat GPTo 
I have, for now, modified the creation date of one of my notifications directly through the database and adjusted settings such that:
-
The first notification (in terms of processing order) does not use “Set Property After Alert”.
-
The second notification processed (in terms of processing order) uses the “Set Property After Alert”.
Both of the notifications, 1 and 2, check the value of the property being set via the Condition setting. I hope this will avoid multiple notifications but suspect it will only work if my understanding about processing order is correct.
Can anyone verify that notifications are in fact processed in the order of their creation date?