#Beginner Developer11 diskutieren mit

 Hi @Akhilesh Prajapati

To improve Email-to-Case reliability and minimize the impact of routing failures, I would recommend the following approach:

1. Maintain an email backup: Configure your email server to retain a copy of every incoming support email in the original mailbox or a dedicated backup folder before forwarding it to Salesforce.
2. Configure a secondary routing option: Maintain a separate backup support mailbox or alternate intake channel. If the primary forwarding configuration fails, your email administrator can redirect incoming emails to the backup route. Test this setup carefully to avoid duplicate cases.
3. Monitor processing failures: Configure the Automated Case User's email address to deliver Salesforce Email-to-Case error notifications to a monitored internal mailbox or distribution group.
4. Enable error notifications: In Setup, navigate to Feature Settings → Service → Email-to-Case and review the option to notify senders about processing errors.
5. Test the Salesforce routing address directly: Send a test email to the generated Email Services Address. If a case is created, investigate the external email forwarding configuration. If no case is created, check the Automated Case User's permissions, record types, validation rules, Apex triggers, and Flow automation.
6. Implement monitoring: Use email-platform monitoring to alert administrators when forwarding rules change or message delivery fails. You can also periodically send test emails and verify that corresponding cases are created.
7. Establish a recovery procedure: During an outage, preserve affected emails and create or resubmit cases after the issue is resolved. Before replaying messages, check whether a case already exists to avoid duplicates.

Salesforce documentation:

• Troubleshooting Email-to-Case: https://help.salesforce.com/s/articleView?id=000384980&language=en_US&type=1
• Email Retention and Error Prevention: https://help.salesforce.com/s/articleView?id=000387063&language=en_US&type=1
• Email-to-Case Forwarding Guidelines: https://help.salesforce.com/s/articleView?id=service.customizesupport_forwarding_guidelines.htm&language=en_US

For a production environment, I would prioritize retaining inbound emails, monitoring processing errors, and documenting a tested recovery procedure before implementing a more complex failover solution.

I hope this helps! If you find this answer helpful, please select it as the Best Answer. 

Thanks, 

Deepak Sachdeva 

Nubys Technology Pvt. Ltd.

Hi CM Seb, 

Two separate root causes here, both well-documented, and both explain your exact symptom (works as admin in Debug, silently does nothing for guest users on the live site). 

1. Record creation not happening: most likely the flow isn't actually enabled for the Guest User profile, even if it "worked" in Debug. 

Profile-level object permissions (Read/Create on Application) are necessary but not sufficient. You also need to explicitly grant the flow itself to guest users, this is a separate step from object permissions: 

   - Experience Builder > Settings (gear icon) > General tab > confirm "Guest users can see and interact with the site without logging in" is checked, then click the guest user profile link. 

   - Under Enabled Flow Access, click Edit, and confirm your Transitional Coach Application flow is moved into the Enabled Flows column (not just present in the Available list). 

   Reference:

   This is the single most common cause of "works when I test it logged in, does nothing for actual guest visitors", the flow needs this explicit enablement separate from object CRUD permissions. 

2. Emails not sending: this is a hard platform restriction, not a config you're missing. 

As of Spring '23, Salesforce permanently removed the "Send Email" system permission from the Guest User profile across ALL orgs, and since permission sets can't be assigned to guest users either, there is no way to grant this back declaratively. This is intentional (anti-spam/abuse prevention for public-facing guest contexts), not a bug. 

   Workaround: don't send the email directly from the guest-context flow. Instead: 

   - Have the guest flow create the Application record only. 

   - Use a separate Record-Triggered Flow on the Application object (After Save), running as an internal/system context, not the guest user, to send the confirmation email. Since this second flow runs on the object trigger rather than in the guest user's session, it isn't restricted by the Guest User "Send Email" removal. 

Given your record creation is also failing (not just email), I'd fix #1 first, that's likely blocking everything, and once records start getting created successfully, wiring up a Record-Triggered Flow for the email (per #2) will resolve the email gap cleanly without depending on guest user email permissions at all.

Hi Pablo, 

You can try below approach that consistently works for the Admin cert: 

1. Start with the official Salesforce Exam Guide, not a course or video series. It's the actual blueprint, breaks down every exam section with its weightage (e.g. Configuration & Setup, Security & Access, Standard/Custom Objects, Sales & Marketing Applications, Service & Support Applications, Activity Management, Data & Analytics Management, Workflow/Process Automation). Study time should roughly mirror those weightings, not be spread evenly. 

   Official Trailhead cert prep trail (mirrors the exam guide section by section):

2. Hands-on Trailhead Playground practice beats passive reading for this exam specifically, since most questions are scenario-based ("what would you configure to achieve X"), not definition-recall. For every module you complete, immediately redo the same task from memory in a fresh Playground without the guide open. 

3. Use Trailhead's own interactive scenario/flashcard trail alongside the modules, it's built specifically for this exam and reinforces recall through spaced repetition rather than just re-reading: 

(same trail includes these interactive study tools) 

4. Join the Trailblazer Community and look for/join a Study Group, Salesforce runs official Admin Study Group sessions periodically that walk through each exam section live, this is Salesforce-endorsed prep, not third-party. 

5. Pomodoro (25-30 min focused blocks) works well specifically because Setup pages and declarative tools have a lot of small, easy-to-conflate settings (e.g. sharing rules vs manual sharing vs role hierarchy), short focused sessions per topic reduce mixing concepts up. 

6. Time commitment: Salesforce recommends 6-12 months of hands-on admin experience before attempting this exam, if you're studying alongside real job exposure, 5-8 focused hours/week is a realistic sustainable pace without burning out; if studying without daily hands-on org access, lean toward more Playground time relative to reading time to compensate. 

7. Don't skip the Certification Program Agreement and exam policies page before exam day, format/logistics questions catch people off guard on exam day itself, not just content:

Good luck, this is a very achievable cert with consistent Playground practice.

@Hitesh SharmaHitesh, for a beginner I recommend this roadmap:

Apex Basics → Variables/Conditions/Loops → List/Set/Map → sObjects → SOQL → DML → Classes → Exceptions → Governor Limits & Bulkification → Triggers → Test Classes → Async Apex → REST/Callouts.

Start with the official Trailhead Quick Start: Apex, then Apex Basics & Database. Trailhead Quick Start: Apex Apex Basics & Database

For reference, use the official Apex Developer Guide.