#Flow173 discussing

That confirms it exactly, Abigail - one hidden character is riding along (16 instead of 15), almost certainly a line break or non-breaking space that got pulled in from the Description. TRIM won't remove those, but CHAR() will. 

Wrap your extracted value in this - either as a Text formula resource, or directly in the formula that feeds your Get filter: 

TRIM(SUBSTITUTE(SUBSTITUTE(SUBSTITUTE({!yourEmailValue}, CHAR(13), ""), CHAR(10), ""), CHAR(160), "")） 

What each piece strips: 

- CHAR(13) = carriage return 

- CHAR(10) = line feed (newline) - this is the most common culprit when copying out of a free-text field 

- CHAR(160) = non-breaking space 

- TRIM() = any normal leading/trailing spaces 

Run LEN() on that formula's output and it should read 15 now. Then point your Get element's filter at this cleaned value instead of the raw one, and it will match. 

If it somehow still shows an extra character, reply back - we can pinpoint the exact one with UNICODE(MID(value, 16, 1)) - but those three cover it almost every time.

Hi Usman - we found the issue.  This flow was a stand alone flow with this URL -  

We need to launch this way -  

The first URL is expecting a record context.  Since we are creating something new, this was not the correct way to do it. 

thank you for attempting to help.  appreciate it.

Hi Jordan - there are two layers here: making the button visible to guests, and letting guests actually run the flow. You'll likely need both. 

1) Show the button to guests (component visibility). In Experience Builder, open the Grant record detail page, click the flow button component, and open its Component Visibility. Right now there's a rule limiting it to logged-in users (an 'is logged in' / audience condition). Remove that filter, or change the audience to everyone, so both guest and authenticated users see it. 

2) Let guests run the flow (the part that's easy to miss). Guest flow access is granted per flow: 

- Experience Builder - Settings - General: make sure 'Guest users can see and interact with the site without logging in' is on, then click the guest user profile. 

- Under 'Enabled Flow Access', click Edit and move your flow from Available Flows to Enabled Flows. Each flow you want guests to run has to be added here. 

- On an LWR site, also go to Workspaces - Administration - Preferences and enable 'Allow guest users to access public APIs'. 

3) Data + context. Guest users have very restricted permissions, so if the flow reads or writes records, set it to run in System Context (Flow - Advanced - How to Run the Flow) so the data actually shows and saves for guests - and make sure the Grant record (and anything the flow touches) is shared with the guest user via a guest sharing rule, or the record page/flow won't load for them. 

4) Test it logged out (incognito) to confirm guests both see the button and can complete the flow. 

Refs: 

- Allow Guest Users to Access Flows:

- Flow (Experience Builder Component):

Hi Swati - nice one to flag. That Winter '27 improvement is the new Flow Builder filter that lets you surface the elements which aren't used and the ones missing descriptions, so you can clear technical debt in one place instead of hunting manually. Really handy for flow hygiene. 

Until it's live in your org, here's how a lot of us handle this today: 

Descriptions: 

- Add a description on every element, resource, and variable as you build (not after), paired with a clear naming convention (e.g. action-object like Get_OpenCases, Decision_IsHighPriority) so the flow reads like its own documentation. Fill in the Flow's own description with its purpose and trigger too. 

Unused elements/variables: 

- The tool that already does almost exactly what the Winter '27 filter will do is the open-source Lightning Flow Scanner - it flags unused variables, missing descriptions, missing fault paths, hardcoded IDs, naming-convention issues, and more, and it can run in CI for a hygiene pass across all your flows now. 

- Salesforce Optimizer also reports on flows, and tools like Elements.cloud help with documentation at scale. 

Broader best practices worth pairing with this: one record-triggered flow per object/context where you can, subflows for reuse, fault paths, bulkification, and tight entry criteria. 

Resources: 

- Trailhead: the 'Build Flows with Flow Builder' trail, plus 'Flow Best Practices' in Salesforce Help. 

- Lightning Flow Scanner (on GitHub) for automated checks. 

Once the Winter '27 filter rolls out (end of August onward per your release window) it'll make the unused/no-description cleanup much faster natively.

@Roopa Sharma

, you can use a formula field that removes dots, hyphens, spaces, and slashes, and uppercases everything and even the Country Prefix (if its not standardized) as Usman mentioned above. Lets call that VATnumber. 

• For Country Prefix, I am assuming billing address is available, so you could use that for country code, since the duplicate match needs to run for CountryCode+VATnumber+RecordType.
• If Country Code is not available, you might want to create a list somewhere with country - VAT prefix (not ideal but should give accurate results)

Also, if possible, add some help text with preferred formatting on the VAT Number field and maybe a validation rule to help end users stick to using only - or .

As per the Salesforce articles and Agentforce all the actions in the flow are not apex actions and can only be used in the flows. The specific scenario that is failing is when a 3 contacts with the same email exist in salesforce and i try to send an email to each via to, cc, and bcc it fails but i dont receive any error either so I assume the activated cloned flow never really runs and to confirm this i have even added task creation to the flow but still no change.