Search

When an Intelligent Advisor interview is submitted, a SOAP request goes out containing many create/update/delete requests in a batch. If an error occurs during that batch, the transaction is rolled back (new objects are removed, updates are undone etc). Business rules can jump the gun and read objects that are being created in a batch before the batch is completed. The Incident is created (in temporary storage) first and, if it doesn't have any validation issues, the remainder of the SOAP request continues being processed. However, business rules have access to the uncommitted Incident already. An email gets sent based on the ID that would be assigned to the Incident, but it gets rolled back. 

As possible solutions, the following suggestions may be considered:

• adjust the rule so it isn't run on-create, instead add some time-gating mechanism to the rule
  • this could be achieved by making use of escalations - Answer Link: Popular Answers about Escalations
• rely on the existence of particular sub-objects to have been created too, by adding a custom object in the IF conditions
• trigger another asynchronous rule with the Incident ID which runs X seconds later, which checks if that ID exists before sending the email
  • you could make use of CPMs - Answer Link: CPM/Process Designer Best Practices and Guidelines