#Metadata2 discussing

Potential Fix for Flow Deployment Error with emailSimple / Send Email Core Action

I ran into an issue when deploying a Flow that uses the Salesforce Flow core action Send Email.

The deployment failed with this error:

Send_Email_to_Users (Action) - We can't find an action with the name and action type that you specified.

The action metadata looked valid:

<actionName>emailSimple</actionName>
<actionType>emailSimple</actionType>

However, the issue ended up being the versionString inside the actionCalls node.

In my sandbox, Salesforce generated the emailSimple action metadata with:

<versionString>3.0.1</versionString>

But in production, the same Send Email action was being generated with:

<versionString>2.0.1</versionString>

After changing the Flow metadata from 3.0.1 to 2.0.1, the deployment completed successfully.

Example:

<actionCalls>
    <name>Send_Email_to_Users</name>
    <label>Send Email to Users</label>
    <actionName>emailSimple</actionName>
    <actionType>emailSimple</actionType>
    ...
    <nameSegment>emailSimple</nameSegment>
    <offset>0</offset>
    <versionString>2.0.1</versionString>
</actionCalls>

So, if you are seeing this deployment error with Flow Send Email / emailSimple, check whether the versionString value differs between sandbox and production.

This looks like an internal version mismatch for Salesforce’s emailSimple core action. The deployment error message does not directly identify versionString as the problem, so it can be easy to miss. 

Built a new Object Explorer experience into Salesforce Metadata Navigator

 to cut down the clicks it takes to inspect object setup. 

You can jump into a specific object’s configuration from anywhere and browse it in a mini Salesforce-style Object Manager layout right inside the extension. Instead of bouncing through multiple Setup pages, you can quickly access: 

• Details
• Fields & Relationships
• Page Layouts
• Lightning Record Pages
• Buttons, Links, and Actions
• Compact Layouts
• Field Sets
• Record Types
• Search Layouts
• Object and Field Access
• Triggers
• Validation Rules
• and more

The goal was simple: reduce navigation time for admins and architects who spend too much time drilling through Setup just to find one object setting. 

It gives you a faster way to inspect metadata, open the exact setup page you need, and move between object-level configurations without losing context. 

If you work across multiple objects every day, this makes admin work feel much more direct and a lot less click-heavy. 

#Salesforce Admin #Trailblazer  #Salesforcearchitects  #Metadata  #Salesforce @* Release Readiness Trailblazers *@* Salesforce Administrators *@Admin Tricks #RRTreasureHunts #New Releases #Automation

Join the March edition of Agentforce NOW Ask Me Anything!

If you have been working with the MCP beta or architecting away from legacy REST integrations, the March edition of our Agentforce NOW session is the technical deep dive for you. 

As Salesforce-hosted MCP servers reach GA this Spring, this month’s edition of our popular Ask Me Anything series will enable developers to expose existing Salesforce logic (Apex, REST APIs, AI, Metadata) as a mix of Tools and Prompts. Product Manager expert @Ross Belmont will showcase moving beyond one-off REST API connectors to standardized, agentic workflows, implementing standards-based authentication for agent-driven operations, and managing governance as the agent landscape scales. 

This is a great opportunity to get into the weeds on operational flow, named credentials, and the security models that make these integrations enterprise-ready. Hosted by Salesforce Developer Advocate @Alba Rivas, they'll answer your questions live during the session.  

Register and join us live here: https://www.linkedin.com/events/7429238805141889024/

*All AMAs are recorded and can be watched on demand on the Salesforce Developers YouTube channel.   #Mcp #RestAPI #Metadata #Prompts #Apex 

Streamline Deployments with DevOps Center: Agentforce NOW Ask Me Anything July 2025 

DevOps Center now integrates with the new DX Inspector, a new management tool within Salesforce sandboxes that enhances metadata tracking and visualization used by Agentforce.  

Join developer advocate host

Date: Wednesday July 30, 2025

Time: 9am PT

Click here to register. 

What to do, when facing the metadata deployment error: 

insufficient access rights on entity: InteractionCustomError?

To whomever might read this, I want to share how to resolve this issue, since I did not find any results online. 

I was successfully able to deploy flows that did not have Custom Error elements, but when trying to deploy a flow, which had this, I faced the above error. I was deploying via sf / sfdx CLI, not via Change Sets. 

The only reason why I found this error, was because I was trying to change the automated deploying user (CI/CD) from a system admin profile to a minimum access profile with added permission sets that allowed for deployment. 

The cause is that the deploying user was missing either:

1. View All Data (something the System Admin profile has), or
2. Manage Flows

I did not want to grant View All Data to the deploying user, but makes sense to add the Manage Flows system permission. 

While it does not make sense, that the deploying user can deploy flows without the Manage Flows permission - that in itself was quite confusing - it does make sense that one would need Manage Flows permission to in general manage flows (including the Custom Errors elements). 

I hope this helps others.