5.6 Application Configuration Troubleshooting

Start With The Symptom, Then Find The Layer

A user says Salesforce is broken, but the underlying issue might be permissions, sharing, record type assignment, page layout, Lightning page visibility, field-level security, validation, duplicate rules, automation, inactive product setup, rule criteria, email deliverability, or feature licensing. Platform Administrators need a repeatable troubleshooting pattern. Do not change random settings until you can reproduce the symptom and name the layer that controls it.

Start by asking who is affected, which record or app is affected, what changed recently, and whether the problem is new or longstanding. Then reproduce as the affected user if permitted. Compare with a known working user. Inspect the exact record type, owner, field values, profile, permission sets, app, page layout, Lightning record page, and automation path. Many issues are caused by a correct setting in the wrong layer.

Sales Troubleshooting Patterns

For Lead issues, check status values, assignment rules, duplicate rules, field mappings, and conversion target requirements. A Lead may save correctly but fail conversion because Account, Contact, or Opportunity validation blocks the target record. A user may be able to view a Lead but lack Create permission on Opportunity. A duplicate rule may warn one user but block another if rule behavior or permissions differ.

For Opportunity issues, identify record type first. If the wrong Stage values appear, check the sales process assigned to the record type. If key fields do not show in Path, check Path settings for the object, record type, and picklist. If a validation rule fires unexpectedly, inspect the formula and the field values at save time. If the user cannot add products, check Product, Price Book, Price Book Entry, Opportunity Product permissions, and multi-currency behavior.

For forecasting issues, do not start with dashboards. A dashboard only reports available data. Check whether forecasts are enabled for the right users, whether role hierarchy or forecast hierarchy includes the rep, whether Opportunities have close dates in the forecast period, whether Amount or Quantity is populated, and whether forecast category is included. A manager cannot forecast what the data model excludes.

Service Troubleshooting Patterns

For Case routing, confirm the Case was created through a path that uses assignment rules. Some manual or API creation paths may require selecting the active assignment rule option or passing a header through integration. Check rule entry order, criteria, owner targets, queue membership, and after-save automation. If Flow updates owner after assignment, the assignment rule may have worked and then been overwritten.

For customer email issues, separate outbound email from Case routing. Auto-response rules require active entries and matching criteria, and the template must be valid. Organization-wide email addresses, deliverability settings, spam filtering, and verified sender configuration can all matter. If an agent email works but auto-response does not, the rule criteria or feature setup may be the issue.

For entitlements, inspect whether the Case is linked to the right Account, Contact, Asset, Service Contract, or Entitlement. Check whether the entitlement is active, whether the entitlement process applies, and whether milestones start, stop, or pause under the expected Case conditions. Business hours and holidays can make elapsed time look wrong if you are counting clock hours.

Reproduce, Change, Verify

A disciplined admin works with focused test records. Clone or create a safe Lead, Opportunity, or Case that matches the issue. Record the current behavior. Change one configuration layer at a time. Test as the affected user. Then update documentation or admin notes so the reason is not lost. This is especially important in orgs where multiple admins and agents are working at once.

Troubleshooting workflow

1. Capture the exact user, record, app, time, and error message.
2. Reproduce the behavior with the same profile, permission sets, and record type.
3. Identify the controlling layer before editing anything.
4. Check recent setup changes, deployments, packages, and automation versions.
5. Make the smallest change that addresses the confirmed cause.
6. Verify with the affected user path and a regression path.
7. Document the cause and any new support steps.

Tools And Evidence

Use Setup audit trail to review recent configuration changes. Use Flow debug and paused or failed flow interviews where relevant. Use field history tracking if it is enabled on important fields. Use login as, permission set assignments, record page assignment details, and Lightning App Builder activation details to investigate UI differences. Use reports to find data patterns, such as Cases without entitlements or Opportunities without products.

For email and web intake, test with simple records before blaming users. Email-to-Case, Web-to-Case, and integrations can supply different field values than manual entry. Assignment rule criteria evaluate the record as created or updated through that path. If a web form does not populate Product, a rule entry based on Product will not match. If an integration uses an inactive record type, page layout testing will not reveal the problem.

Scenario Walkthrough

A rep says the discount field disappeared from Opportunities. Another rep sees it. The wrong fix is to add the field everywhere immediately. The disciplined path is to compare profile, permission sets, record type, page layout assignment, field-level security, dynamic form visibility, and Lightning page activation. If the field is hidden by FLS for one permission set group, adding it to the layout will not help.

A support manager says urgent web Cases are not escalating. First confirm the Cases match the criteria, are not already closed or paused, use the expected business hours, and are linked to the right entitlement or escalation rule. Then check whether an after-save Flow changes Priority or Status after creation. Most application troubleshooting is not about knowing a secret setting; it is about finding the layer that owns the behavior.