after making updates to a process builder for task record inserts, I am trying to deploy it - using change sets - to the Testing sandbox from our Development sandbox. The previous deployment - which contained 9 Email Alert immediate actions - worked fine in Testing sandbox and is presently activated and has been running for about a month now.

However, after adding a couple more conditions (that use Text Field Immediate Actions) on the Development Sandbox's process builder today, I am getting this error during deployment to Testing sandbox: myRule_1_A1 (Action) -We can't find an action with the name and action type that you specified. I have no idea why the process builder is not deploying. Here are some screen scrapes of the updates I made to the process builder. enter image description here enter image description here

  • between the target and source org, have you renamed any of the Process Builder or Email Alerts?
    – cropredy
    May 28 '20 at 0:07
  • The error is probably not coming from this newly added node. May 28 '20 at 1:16
  • @cropredy I have reinspected this and I don't see any naming differences for the email alerts between Development sandbox and Testing sandbox. May 28 '20 at 12:45
  • I have the same problem with flow. The flow call apex method and get sorted records. When I try to deploy my changes to another sandbox have same problem "Error:(1, 1) Catch_Same_Products (Action) - We can't find an action with the name and action type that you specified." P.S. All files were deployed in the sandbox before I tried to deploy my flow.
    – user89595
    2 days ago

I'll add another possible reason for this (as it happened to me today):

Deploying a Flow with actions that included sending emails. These require an Workflow Email Alert to be deployed but if the Workflow is not part of the deployment package, the deployment fails with a message that starts with:

We can't find an action with the name and action type that you specified

Thanks to all @cropredy and @hengky for their help and I guess both of them were partly correct but here is the full answer. Unbeknownst to me,one of the client's SF Admins had created a new email alert which uses my email template tht my process builder somehow uses. Furthermore, I believe it may also be somehow overriding my original email alert because it is sending out email notifications not just to the assignee of the Task but also CC'd email addresses. So the issue basically was that an email alert - that I did not create - was not put into the change set. Solution: Add that email alert into the change set.


You will also have to include the Email Template if not already ported. I also had an issue with non-matching user names so used an 'additional' email address. Once ported, I added back the Users.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.