[SalesForce] How to track down an internal server error

I'm getting an internal server error message, wondering how I track down the cause?

I have a custom lightning component (lwc) that runs fine when dropped into a tab on a Campaign record page. Previously, it also worked when dropped into a tab on a custom object record page. Now, I'm getting an error when I try to load that record page (or any record page for that custom object).

If I go into Lightning App Builder (LAB) and pull the component off the page, it loads fine, so it's something to do with my component.

In LAB, I can drop it into the tab, and I see that it loads up fine. It generates logs that I can see, successfully reading the page's recordId and calling Apex for data. Looks great in LAB. Saved, activated, return to the main record page, and nothing on that page loads. Instead, I get this error:

Looks like there's a problem.

Unfortunately, there was a problem. Please try again. If the problem
continues, get in touch with your administrator with the error ID
shown here and any other related details. An internal server error has
occurred Error ID: 1717890395-229230 (-1122514613)

So, what's the procedure/resource for tracking down an error when you have the ID?

Best Answer

It sounds very similar to this post? So I am thinking there is some bug with summer 19. Though I tried to re-create and couldn't - so not sure if it is an instance thing, a namespace issue or something else?

If you have access to Partner Support, I would raise a case there. Typically, regular support won't accept Dev Support requests (even though it is a bug - a group of us in community are trying to get that changed, but it's an issue for now)

Might also be worth posting in the Lightning Web Component Group in success since that seems fairly active https://success.salesforce.com/_ui/core/chatter/groups/GroupProfilePage?g=0F93A000000LlT2

Related Solutions

[SalesForce] Visualforce Error dealing with visual flow and custom button

Salesforce Support finally responded with this fix:

To address the error, Tier 3 has updated the Screen Choice Field from 'Contact' to 'Contact2' of 'Service Contract Flow'.

Please apply the same workaround to the other Flows that throw the error. Also, do not use the same dev name of your Choice Lookup anywhere else in your flow.

Here is the link to the known issue:

https://success.salesforce.com/issues_view?id=a1p30000000T4RaAAK

As noted on the page, it has a scheduled patch in the Summer '14 Release.

[SalesForce] sObject array parameter in Lightning causes Internal Salesforce.com Error in Apex controller

The problem is deep inside of the transport/marshalling interface layer between Lightning Components and Apex and will need to be fixed by my team.

For now I have developed a generic workaround using a small amount of Apex.

public class OneLeadController {

    @AuraEnabled
    public static Id createLead(Lead newLead) {
        insert newLead;
        return newLead.Id;
    }

    @AuraEnabled
    public static List<Id> createLeads(String newLeads) {
        List<SObject> newSObjectsList = convertJSONToListOfSObject(newLeads);

        insert newSObjectsList;

        List<Id> newIds = new List<Id>();
        for (SObject o : newSObjectsList) {
            newIds.add(o.Id);
        }

        return newIds;
    }

    @AuraEnabled
    public static Lead newLead() {
        return (Lead)Lead.sObjectType.newSObject(null, true);
    }

    private static List<SObject> convertJSONToListOfSObject(String json) {
        Object[] values = (Object[])System.JSON.deserializeUntyped(json);

        List<SObject> newSObjectsList = new List<SObject>();
        for (Object v : values) {
            Map<String, Object> m = (Map<String, Object>)v;

            Schema.SObjectType targetType = Schema.getGlobalDescribe().get((String)m.get('sobjectType'));

            SObject o = targetType.newSObject();

            Map<String, Schema.SObjectField> fields = targetType.getDescribe().fields.getMap();
            for (String fieldName : m.keySet()) {
                // Filter out any psuedo fields such as LastNameLocal
                Schema.SObjectField fi = fields.get(fieldName);
                if (fi != null) {
                    if (fi.getDescribe().isCreateable() && fi.getDescribe().isUpdateable()) {
                        o.put(fieldName, m.get(fieldName)); 
                    }
                }
            }

            newSObjectsList.add(o);
        }

        return newSObjectsList;
    }
}

and a small corresponding change to the client side controller (oneLeadController.js) calling this:

({
    save : function(component, event, helper) {
        var self = this;

        var createLeads = component.get("c.createLeads");
        createLeads.setParams({
            "newLeads": $A.util.json.encode(component.get("v.leads"))
        });

        createLeads.setCallback(self, function(a) {
            if (a.getState() === "SUCCESS") {
                console.log("returned: %o", a.getReturnValue());
            } else {
                alert($A.util.json.encode(a.getError()));
            }
        })

        $A.enqueueAction(createLeads);
    }
})

Related Topic