One way to avoid “Term update failed because of save conflict” error when create managed metadata terms in Sharepoint

In one of the project we used the following PowerShell CSOM code for creating managed metadata navigation terms in Sharepoint Online:

   1: $newTerm = $navTermSet.CreateTerm($web.Title,

   2:     [Microsoft.SharePoint.Client.Publishing.Navigation.NavigationLinkType]::SimpleLink,

   3:     [System.Guid]::NewGuid())

   4: $newTerm.SimpleLinkUrl = $web.ServerRelativeUrl

   5: $termStore.CommitAll()

   6: $ctx.ExecuteQuery()

It worked successfully for many tenants but for one tenant it gave the following error:

Exception calling "ExecuteQuery" with "0" argument(s): "Term update failed because of save conflict."

Error appeared randomly, i.e. for the same sub site some time term has been created successfully and some time it failed with above error. There were no other changes so the reason was not in pending changes.

In order to avoid this error we applied the following workaround:

   1: do

   2: {

   3:     Try

   4:     {

   5:         $newTerm = $navTermSet.CreateTerm($web.Title,

   6:             [Microsoft.SharePoint.Client.Publishing.Navigation.NavigationLinkType]::SimpleLink,

   7:             [System.Guid]::NewGuid())

   8:         $newTerm.SimpleLinkUrl = $web.ServerRelativeUrl

   9:         $termStore.CommitAll()

  10:         $ctx.ExecuteQuery()

  11:         break

  12:     }

  13:     Catch

  14:     {

  15:         Write-Host "Error occured, try one more time" -foregroundcolor yellow

  16:     }

  17: } while ($true)

I.e. instead of single call to CreateTerm and ExecuteQuery we call it in the loop until call will be successful. Log showed that with this approach all navigation terms have been created properly at the end although for some sub sites it failed 1 time, for other 2 and for some even 3 times until it created term successfully, while for most of sub sites there were no errors at all. Hope that this engineering approach will help some one:).