#Salesforce Developer374 discussing

@Prasanna Achar

Yes, it does work differently in sandbox. Your Flow, licenses, and config are all fine, which is exactly why you get a success report with no errors. The message just never physically leaves the platform.  

The actual SMS carrier provisioning, the phone number, and the live connection to the messaging provider behind Digital Engagement are tied to your production org.  Sandboxes get the config metadata copied over, so the Channel, number, and Messaging Component all look active and valid, but the live carrier binding doesn't exist in the sandbox.  

Confirm with Salesforce whether SMS is actually provisioned for your specific sandbox. Usually it isn't by default, and real outbound SMS only sends from production. Some orgs can request a sandbox be provisioned for messaging testing, but it's not automatic and often not available. Thanks! 

@durgam santhosh

Yes - the native no-Apex route is an Email Alert (the core 'Send Email' Flow action won't render a template's merge fields). Create an Email Alert on Opportunity (Setup > Email Alerts) that uses your Opportunity Lightning template, then call it from your record-triggered Flow as an Action - the alert sets the triggering Opportunity as the Related To, so all your Opportunity merge fields resolve. 

For recipients you can pick Opportunity Owner directly; to send to that custom email field it has to be an Email-type field, then it shows up under Recipient Type 'Email Field'. 

If this helps, please mark it as the Best Answer so it helps the next person - thanks!

If anyone sees this, then according to the documentation:

https://developer.salesforce.com/docs/atlas.en-us.field_history_retention.meta/field_history_retention/field_audit_trail.htm

Salesforce retrieves only custom retention policies with the object definition.

You might need to change the retention policies from their default value (18 months, 10 years etc.)

@Commerce Trailblazers @* B2C Commerce * @* Commerce Salesforce Order Management * @Serviceblazer Community Group @MomentMarketer Community Group @* Salesforce Developers * @Trailblazer Community Cove @Trailblazer Community Cove@* Salesforce Administrators *@* Salesforce Developers * @* Salesforce Platform * @* Trailhead Academy * @Newbie Tableau User Group Desktop @Tableau Analytics @Tableau Announcements @Slack Beginners @Slack + Agentforce @Salesblazer Community Group @Agentblazer Community Group @* B2C Commerce * @* Salesforce Commerce for B2B & D2C * @* Salesforce Revenue Cloud * @* Data 360 * @* Sales Cloud - Getting Started * @* Sales Cloud - Best Practices * #Trailhead #AI #Agentforce #Salesforce Developer #Salesforce Admin

Great question, Brandon. From a cost/benefit perspective, I’d avoid sending every Nebula Logger record to Datadog without first confirming which level of detail your monitoring and troubleshooting actually require. 

If you’re primarily interested in exception visibility, LogEntryEvent__e may provide the event-level information you need, while Log__c and LogEntry__c can be valuable for retaining and correlating the broader logging context within Salesforce. Sending everything could improve traceability but may also increase data volume, storage, and Datadog ingestion costs. 

For the realtime vs. scheduled question, I’d verify the specific Nebula Logger/Datadog integration implementation and configuration rather than assuming from the object type alone. Platform Events can be delivered asynchronously, but the integration architecture determines whether Datadog receives them immediately or through a polling/scheduled process. 

Interested to hear what others have observed with this integration as well!  

Hi @Roopa Sharma -  It’s not possible through standard Salesforce configuration because the recipient hover tooltip in the Lightning Email Composer is part of Salesforce’s standard UI. 

Salesforce doesn’t expose a setting or Email Action field configuration that lets an admin control what appears in that tooltip. You can configure the email fields such as To, CC, BCC, Subject, and Body, but not the content of the recipient hover popup. 

So: 

• Standard configuration: Not possible 
• Flow: Cannot modify it 
• Email Action settings: Cannot modify it 
• Custom LWC: Possible, if you need the email address displayed on hover 

The limitation is with the standard Lightning Email Composer UI, not with the Contact/Lead email field itself. 

Hi Ritika,

Based on the symptoms you described—0 Subagents, an empty New dropdown, no Agent Actions/Subagents in Setup, and the “Invalid user ID provided on start session” error—this may be related to the provisioning or configuration of the special Agentforce Developer Edition org rather than the Apex classes themselves. 

Please first confirm that you’re using the special Developer Edition org provided specifically for this badge and that all prerequisite setup steps have been completed. You can also try refreshing the org and logging out/in again. 

If the Subagents and Agent Actions are still unavailable after verifying the setup, please provide more details about the steps completed and any relevant screenshots. If the issue persists, it would be best to create a Salesforce Support case for further investigation.