#Deployment3 discussing

☀️ IN-PERSON SUMMER NETWORKING EVENT 

 📅 July 24 | 🕞 3:30–6:00 PM | 📍 Divine Barrel Brewing

 🍕 Food and drinks are included! 

🎲 Take the gamble out of your next Salesforce deployment!

Join the Charlotte Salesforce Admin Group for Release Survival: Taking the Gamble Out of Salesforce

Deployments & Summer Networking.

We’re excited to welcome Flosum (@Scott Cotter) for a featured presentation on practical ways to make Salesforce releases more predictable, reduce deployment risk, and avoid the last-minute surprises that can turn release day into a roll of the dice.

After the presentation, stick around for summer networking with fellow Salesforce professionals from across the Charlotte community. Whether you are an admin, developer, consultant, or simply looking to learn from others, we would love to see you there. 

☀️ Learn something new 

 🎤 Hear from the Flosum team 

 🤝 Connect with the community 

 🍕 Enjoy complimentary food and drinks 

 🎲 Leave release-day gambling behind 

Register here:

 https://trailblazercommunitygroups.com/events/details/salesforce-salesforce-admin-group-charlotte-united-states-presents-release-survival-taking-the-gamble-out-of-salesforce-deployments-amp-summer-networking/

Please RSVP only if you are confident you can attend, as in-person space is limited. 

#Devops  #Deployment  #Release Readiness  #Release Management

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. 

Phishing Resistant MFA

For those who are looking clarity about Phishing Resistant MFA which as stated by Salesforce will take effect on:

• Sandboxes: Starting June 22, 2026, staggered over approximately 7 days
• Production: Starting July 1, 2026, staggered over approximately 30 days

Sharing some clarity. Hope it will be useful for you guys!

They must comply with Phishing Resistant MFA, meaning when loging in with SSO in SAML response any of this values should be present: cert, fido, fido2, fpt, hwk, iris, pin, pki, pop, retina, sc, Smartcard, swk, TLSClient, user, vbm, wia, X509. 

Privileged Users (with Modify All Data, View All Data, Customize Application, Author Apex permissions) with UI logins: 

They must comply with Phishing Resistant MFA meaning when loging in with SSO in SAML response any of this values should be present: cert, fido, fido2, fpt, hwk, iris, pin, pki, pop, retina, sc, Smartcard, swk, TLSClient, user, vbm, wia, X509. 

Integration Users 

All Integration Users must use API Only User to bypass this requirement (User, not the connected app) if someone is actually loging in. If they don't have it, they must comply with Phishing Resistant MFA meaning when loging in with SSO in SAML response any of this values should be present: cert, fido, fido2, fpt, hwk, iris, pin, pki, pop, retina, sc, Smartcard, swk, TLSClient, user, vbm, wia, X509. If no logins are performed (you can check such integration users login history), then no impact should be visible on them.  

To check what values in the SAML Response you are receiving with user logins, you can try and use some SAML response analyzer tool, for example I'm using SAML Tracer (chrome extension) 

https://chromewebstore.google.com/detail/saml-tracer/mpdajninpobndbfcldcmbpnnbhibjmch?hl=en

Hope this clears things out for you! 

Source:

https://help.salesforce.com/s/articleView?id=005321563&type=1

and discussions with Salesforce Support 🫡 

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.