#Trailhead604 人がディスカッション中

Hi Angel - good news: this is expected platform behavior, not a bug in your org, and it probably won't actually block the challenge. 

Why you can't deselect it: Salesforce now enables 'Require Proof Key for Code Exchange (PKCE)' by default and makes it non-editable on External Client Apps. It's part of the secure-by-default hardening (the OAuth 2.1 direction), so every org behaves this way now - a fresh Playground would be the same. So you're not doing anything wrong; the greyed-out checkbox is just the current default. 

What to do: run Check Challenge with PKCE left on anyway. The validator for this step checks things like the app's name, OAuth scopes, callback URL, and the flows you enabled - not whether PKCE is switched off. So even though the older instructions may tell you to uncheck it, the challenge usually still passes with it on. Try that before assuming you're stuck - I'd bet it goes green. 

If it genuinely fails on that step: this is a known gap where the platform changed but the module text hasn't caught up yet. The right channel is a Trailhead Help case - they're who can look at a challenge that won't validate. One quick note: this Trailblazer group is peer Trailblazers, not Salesforce Support, so posting an Org ID here won't reach Support; Trailhead Help via the Help site is your fastest route, and you don't need to share your Org ID publicly to get it looked at. 

Hope that unblocks you!

Hey Ayush, 

This specific "Something went wrong / Error ID" message when opening Flow Builder is usually a client-side caching or session issue, not a problem with the flow itself, especially since it shows as a valid Draft version. 

Things to try in order: 

- Navigate to it the exact way the module specifies: App Launcher > search Flows > All Flows list view > click the flow name (not directly from Setup > Flows) > then click Open Flow. Sometimes opening via a different path in Setup can trigger this error where the proper navigation path doesn't 

- Hard refresh (Ctrl+Shift+R / Cmd+Shift+R) then try again, this clears cached Lightning/Aura component state that commonly causes these generic numeric Error IDs 

- Clear browser cache and cookies for the domain specifically, or try Incognito/Private window 

- Try a different browser entirely, this error is often tied to a corrupted local cache specific to one browser profile 

- If it persists, log out of the org completely and log back in, this forces a fresh session token, which resolves this error in a lot of reported cases 

If none of that works, this could mean the flow itself has a corrupted element (sometimes caused by objects/fields referenced in the flow not existing yet, which matches your situation since the flow references Data 360 objects that only exist after your data streams were set up). Double check that your Data Cloud data streams and identity resolution steps from earlier in the project fully completed and are showing data, an incomplete dependency can sometimes cause Flow Builder to fail loading rather than just showing a field error. 

Reference:

Hey Casey, 

Speaking from what tends to work well across service businesses, the short answer is: no single channel does it alone — the combo that builds the most trust is usually in-the-moment explanation + a simple written follow-up. 

A few observations on what actually moves the needle: 

In-person/on-site explanation during service 

This is consistently the highest-trust channel, since customers see it happening in real time (e.g., a technician showing which parts get recycled vs. landfilled). The catch is it's inconsistent — quality depends entirely on that one employee's habits that day. 

Follow-up email/text after the job 

This is where a lot of businesses win extra trust cheaply. A short "here's what we did with your old unit/materials" note sent right after service reinforces what was said verbally and gives customers something to reference or forward to others. Doesn't need to be fancy — a templated paragraph works fine. 

FAQ/blog content 

Good for pre-service research (people looking you up before booking), but it rarely gets read post-service, so it's more of a trust-building/SEO tool than an education tool for existing customers. 

Printed guides/inserts 

Still works well for older demographics or in industries where the customer keeps physical paperwork (invoices, receipts), but it's the weakest for younger customers who just archive digital receipts and never look back. 

If you had to pick one high-leverage combo: verbal explanation at time of service + a short automated follow-up email summarizing it. The verbal part builds immediate trust, the email gives it permanence and something shareable/reviewable, which is what tends to actually shift customer behavior over time (not just perception). 

 Une cause fréquente est de calculer directement en heures plutôt qu'en minutes. Essayez de convertir toutes les valeurs (heures de début, de fin et pauses) en minutes, puis effectuez les calculs avant de reconvertir en heures décimales à la fin.  

Pour les horaires qui passent minuit, ajoutez 24 heures lorsque l'heure de fin est inférieure à l'heure de début. Vérifiez également que la durée totale des pauses ne dépasse jamais le temps travaillé. Cette approche permet généralement d'éviter les valeurs négatives et les erreurs d'arrondi dans les Flows.