Brief Screen Goes Blank When Adding New Solution Due to Static Resource Loading Failures

Symptom

When adding a new solution to a Brief in the Solution Console:
- The screen goes blank or displays a white screen
- A circular loading icon may appear but the solution never loads
- The issue occurs intermittently - sometimes the solution loads correctly, other times it fails
- Browser console shows 404 Not Found errors for static resources

Example console errors:

GET https://<instance>.salesforce.com/resource/<timestamp>/sceditorreact/... 404 (Not Found)

Cause

Salesforce is failing to serve static resources (JavaScript, CSS, HTML files) from the CloudSense managed packages at random. The issue is caused by Salesforce's server-side resource caching mechanism:

• Static resources are loaded with dynamic timestamps (when configured with "rnd" mode)
• Salesforce's resource server intermittently returns 404 errors for valid resource paths
• Different resources fail to load on each page reload
• When critical JavaScript files fail to load, the Solution Console cannot initialize, resulting in a blank screen

This is a Salesforce platform issue, not a CloudSense application defect. The same resources load successfully when accessed directly via URL, confirming they exist but are not being served consistently.

Resolution

Workaround: Force Static Resource Caching

Update the static resource timestamp configuration to use a fixed value instead of random timestamps. This forces Salesforce to cache resources consistently.

Step 1: Access JSON Settings Custom Setting

1. In Salesforce Setup, search for "Custom Settings"
2. Click Manage next to csutil__Json_Settings__c
3. Click New (if no record exists) or Edit (if record exists)

Step 2: Update SCEditor Static Resource Timestamps

Locate all settings related to SCEditor static resources. Look for fields containing:
- SCEditor
- sceditorreact
- sceditor

For each setting, find the csutil__json_configuration__c field value and update any timestamp parameters.

Before:

{
  "staticResourceTimestamp": "rnd",
  ...
}

After:

{
  "staticResourceTimestamp": "1",
  ...
}

Alternatively, you can query and update via Anonymous Apex:

List<csutil__Json_Settings__c> settings = [
    SELECT Id, Name, csutil__json_configuration__c
    FROM csutil__Json_Settings__c
    WHERE Name LIKE '%SCEditor%'
];

for (csutil__Json_Settings__c setting : settings) {
    if (setting.csutil__json_configuration__c != null) {
        setting.csutil__json_configuration__c = 
            setting.csutil__json_configuration__c.replace('"rnd"', '"1"');
    }
}

update settings;

Step 3: Clear Browser Cache

1. Open your browser's Developer Tools (F12)
2. Right-click the Refresh button
3. Select Empty Cache and Hard Reload
4. Alternatively, clear all Salesforce-related cached data from browser settings

Step 4: Test the Resolution

1. Navigate to the Brief Console
2. Create a new Brief or open an existing one
3. Click Add New Solution
4. Verify the solution loads without the screen going blank
5. Check the browser console - no 404 errors should appear for static resources

Step 5: Escalate to Salesforce (If Issue Persists)

If the workaround does not resolve the issue:

1. Open a case with Salesforce Support (Priority 1 - Critical)
2. Reference: "Intermittent 404 Not Found errors for static resources in Visualforce pages"
3. Provide:
4. Org ID
5. Example static resource URLs failing with 404
6. Screenshots of browser console showing 404 errors
7. Confirmation that resources load successfully when accessed directly
8. Request investigation into Salesforce's static resource delivery mechanism

Additional Notes

• Development Mode: If you need to load updated static resources during development (to avoid caching old versions), you can switch back to "rnd" mode temporarily. Remember to switch back to "1" after development is complete.
• Frequency: This issue typically occurs more frequently in sandbox environments (especially Full Copy sandboxes) but can also affect production intermittently.
• Impact Radius: If multiple users report the same issue simultaneously, it indicates a broader Salesforce platform issue rather than org-specific configuration.
• Managed Package Logs: Enabling managed package debug logs will NOT help diagnose this issue, as the problem is with Salesforce's static resource server, not CloudSense application logic.
• Alternative Diagnosis: Use browser Network tab to identify which specific static resources are failing to load. This information is useful when escalating to Salesforce.

Prevention

• Monitor Salesforce Trust status page for any reported issues with static resource delivery
• Keep Solution Management package updated to the latest version (36.4.x or newer includes fixes for related white-screen scenarios)
• Document any patterns (time of day, specific users, specific browsers) if the issue recurs