Hi Bryan,

- Copy one of the GUID values shown on your screenshot

- If your parameter "LOG_EXCEPTIONS_TO_DB" is set to true, Open the "Search Exceptions" screen an look for this GUID

- If you cannot search for Exceptions logged in DB, go check in your Server Logs for the GUID value

If you find the exception details, hopefully you'll get more details about what is actually causing the problem. Most likely some tokens might not be resolved properly during mass update, but the logs should tell you more about the exact root cause. 

Hi Etienne,

Thanks for your response.

I tried to search one of the GUIDs but I got the below message. I also tried to search the GUID in the serverLog but there is nothing in the logs about the GUID Im searching.

Is there any other exception in Server logs around the time at which you reproduce the issue?

I checked and unfortunately no other exceptions found during the time I reproduce the issue.

So you'll want to open a support ticket to get that looked into.

I assume that the problem should not appear if you disable the rule for the time of the mass update, but I also expect that you'll want this rule to fire, even during mass update, so that may not be an option.

Yeah, I will open a ticket for this. Appreciate your response on this.

I also tried to disable that rule and the Mass Update is working as expected without any error.

But unfortunately, that Apply before save Rule is needed that's why we want to do the Bulk Save.