Hi,

Greetings to you!

This might be because of this known issue: https://success.salesforce.com/issues_view?id=a1p3A0000003du0QAA

Internal Server Errors can be hard to debug. An internal error code means that an exception/error occurred that wasn't handled by the platform so it can be very difficult to try to identify which part of your code is triggering the error. But most of the times they are caused by simple mistakes. You can check your code where there are configurations involved.

The best way to get the quick turn around on this.

First Method: Set-up the debug log for the user who is getting this error, if you suspect that this is due to APEX / VF/ SOQL or any other operation then set the same “FINEST” in the log level.
Try to reproduce the error and analyze the debug log to check the root cause.

Second Method: If debug log won’t give you much information about this error then you have the only way to resolve it in less time which is to log a case with Salesforce support.
Please share the below information on your case to get the quick response on it.

• Login access of your affected org(in which the issue is occurring).
• Complete steps to reproduce the error again.
• Complete error message with error ID.
• Attach the snapshot of the error on the case
• Provide your availability hours.
• Date and time when the error occurred the first time.

Support will track the stack trace at your org instance and try to find out the root cause of the error and suggest you the appropriate solution for the error.
The above information will help them to filter out the server logs.

Reference: https://ashutoshsfdc.wordpress.com/2017/05/30/internal-server-error-error-id-1433747999-1629-95108586/

I hope it helps you.

Kindly let me know if it helps you and close your query by marking it as solved so that it can help others in the future. It will help to keep this community clean.

Thanks and Regards,
Khan Anas