Hello,
We are getting the “Record has changed” err...
# suitescriptv
Viraj Shinde
10/18/2022, 2:56 PMHello,
We are getting the “Record has changed” error in one of our environments when we try to save a Sales Order (probably because many scripts are running on Sales Order).
What can be the most efficient way to implement a ‘re-try save’ mechanism for such an error?
Viraj Shinde
10/18/2022, 2:58 PMDo we re-try saving in the same script where we get this error? Or maybe in a UE script where this error can be caught?
Currently I can only think of catching this error in the same script, and calling the save() method again if the error is caught. But I somehow feel that there might be better ways to do this.
b
battk
10/18/2022, 3:57 PMim guessing this is from a scheduled script or map/reduce script
battk
10/18/2022, 3:58 PMin which case the usual is starting over and loading the record again
👍 1
battk
10/18/2022, 4:01 PMthe error is fairly common when the task is started from a user event and there are other after submit user events or after record submit workflows
battk
10/18/2022, 4:02 PMit also means the performance of that record has been trashed if something from the script processor queue is running at the same time as those scripts.workflows
v
Viraj Shinde
10/19/2022, 11:25 AMyes you are right, it originates from a scheduled script
Viraj Shinde
10/19/2022, 11:26 AMthanks for the inputs, i also believe that it has something to do with the overall performance
Viraj Shinde
10/19/2022, 11:26 AMfor now, I will add code to re trigger the load-save part of the script
s
Shubham S
10/26/2022, 2:13 PMIn my case it was in beforeLoad when i was loading and saving the rec if same in your case just try some alternate for it