Unable to update the distributed owner's name in the automation

Issue: Customer was using an automation to update the assigned lead owner to the specific field.

RCA: Customer was using incorrect mail merge for the owner (@{Owner:EmailAddress ,}  @{Owner:FirstName ,}), because of which was values are getting captured as a blank.

Solution: Suggested to use the correct schema => @{Lead:OwnerIdName,}.

• Related Articles

• Automation not trigger on owner/Lead update

  Hi Team, You may encounter an issue where Automation has not triggered on Lead update, where the field will be owner update. Reason To Debug this please check the owner update is done by which card/method. If Owner has been updated by "Lead ...

• Automation Cards Failure email alerts

  The Automation Failure notification will trigger only those who created the automation and who modified the automation. Please note all the users who modified the automation will get the automation failure notification (e.g.: if user-a modified the ...

• Opportunity owner update failure in the UI

  When an opportunity owner is tried to update "1 opportunity failed to update" error is shown. Whereas when the owner is updated via API it is successful. This happens because of the duplicate detection rule. If there are duplicate opportunities then ...

• Incorrect First Name Sent in the Email

  Issue Summary: 1. Customer has created one template, in that template he mail merged first name field. 2. Customer has sent emails in bulk. 3. After sending the email, we observed that all the leads system has updated the same " first name " dynamic ...

• unable to publish an automation, it says it cannot be published because it creates an infinite loop

  Issue: While publishing the automation we are getting an error "creates an infinite loop". Observation: We are encountering an issue where we are unable to publish an automation, it says it cannot be published because it creates an infinite loop. PFB ...