Skip to main content
steve_davis
steve_davis
Gainsight Employee ⭐️⭐️
November 8, 2016

Rule ID's for Failures

  • November 8, 2016
  • 4 replies
  • 56 views
I have a couple customers that have workflows setup on the backend. Sporadically, we get an error message i.e. "Unable to gain exclusive access to this record". The spreadsheet does not contain the ID's for the records that actually failed and the rule usually just partially fails. 

Its typically caused by another process updating the record at the same time, we have to yield to these workflows and because it isn't often knowing which ones failed would be helpful. 

      4 replies

      sundar
      sundar
      Expert ⭐️
      December 12, 2016
      Steve - This would be a good feature request for Salesforce. I faintly remember that someone from Gainsight put this thru, was there any response? 

      There is absolutely no control given by SF nor the detail of which record ID. We are kinda helpless here.
      einat_pick
      einat_pick
      Contributor ⭐️⭐️⭐️⭐️⭐️
      March 16, 2017
      This is really needed.
      I don't understand how can this be managed if you cannot know what are the records that cause the failure?
      einat_pick
      einat_pick
      Contributor ⭐️⭐️⭐️⭐️⭐️
      June 28, 2017
      Adding to my previous comment, such failures can prevent many processes in GS that are dependent on a value that was not pushed.
      For example, CTA creation, Score updates, etc.
        samantha_braastad
        samantha_braastad
        Contributor ⭐️⭐️⭐️⭐️⭐️
        August 20, 2018
        We have seen the same behavior from Rule Engine when a rule fails to run due to a 'Load to SFDC Object' action. Our examples seem to be when new object validations are added preventing Gainsight from being able to save the record without a valid value in a different field. The rule may fail 4-5 records but if we pull a report in SF for that validation, their can be hundreds making it difficult to know which records need to be updated for our purposes only. 
        Terms & ConditionsAccessibility statement