deleted 19 characters in body
Source Link
Keith C
  • 127.3k
  • 19
  • 164
  • 343

This:

Error ID: 1867462533-18494 (-412090138)

is what Salesforce term a gack - see the official documentation What Is A Gack?. It is basically a condition that isn't handled well by the platform. While it would be great if Salesforce fixed the platform every time one occurs, in practical terms changing your code to avoid the problem is the more realistic approach.

You could go it alone and make somewhat random changes i.e. review your code and compare with specs and other code and make changes. Or you could engage with Salesforce support so they can lookup their internal logs using the id values in the message and so hopefully narrow down the problem area and guide you to the code to modify; that may take a couple of days. Going that route, it could also turn out to be a platform bug for which there is no work-around resulting in a patch platform fix (weeks later) or a fix in a future platform release (months later).

This:

Error ID: 1867462533-18494 (-412090138)

is what Salesforce term a gack - see the official documentation What Is A Gack?. It is basically a condition that isn't handled well by the platform. While it would be great if Salesforce fixed the platform every time one occurs, in practical terms changing your code to avoid the problem is the more realistic approach.

You could go it alone and make somewhat random changes i.e. review your code and compare with specs and other code and make changes. Or you could engage with Salesforce support so they can lookup their internal logs using the id values in the message and so hopefully narrow down the problem area and guide you to the code to modify; that may take a couple of days. Going that route, it could also turn out to be a platform bug for which there is no work-around resulting in a patch platform fix (weeks later) or a fix in a future platform release (months later).

This:

Error ID: 1867462533-18494 (-412090138)

is what Salesforce term a gack - see the official documentation What Is A Gack?. It is basically a condition that isn't handled well by the platform. While it would be great if Salesforce fixed the platform every time one occurs, changing your code to avoid the problem is the more realistic approach.

You could go it alone and make somewhat random changes i.e. review your code and compare with specs and other code and make changes. Or you could engage with Salesforce support so they can lookup their internal logs using the id values in the message and so hopefully narrow down the problem area and guide you to the code to modify; that may take a couple of days. Going that route, it could also turn out to be a platform bug for which there is no work-around resulting in a patch platform fix (weeks later) or a fix in a future platform release (months later).

added 2 characters in body
Source Link
Keith C
  • 127.3k
  • 19
  • 164
  • 343

This:

Error ID: 1867462533-18494 (-412090138)

is what Salesforce term a gack - see the official documentation What Is A Gack?. It is basically a condition that isn't handled well by the platform. While it would be great if Salesforce fixed the platform every time one occurs, in practical terms changing your code to avoid the problem is the more realistic approach.

You could go it alone and make somewhat random changes i.e. review your code and compare with specs and other code and make changes. Or you cancould engage with Salesforce support so they can lookup their internal logs using the id values in the message and so hopefully narrow down the problem area and guide you to the code to modify; that may take a couple of days. Going that route, it could also turn out to be a platform bug for which there is no work-around resulting in a patch platform fix (weeks later) or a fix in a future platform release (months later).

This:

Error ID: 1867462533-18494 (-412090138)

is what Salesforce term a gack - see the official documentation What Is A Gack?. It is basically a condition that isn't handled well by the platform. While it would be great if Salesforce fixed the platform every time one occurs, in practical terms changing your code to avoid the problem is the more realistic approach.

You could go it alone and make somewhat random changes i.e. review your code and compare with specs and other code and make changes. Or you can engage with Salesforce support so they can lookup their internal logs using the id values in the message and so hopefully narrow down the problem area and guide you to the code to modify; that may take a couple of days. Going that route, it could also turn out to be a platform bug for which there is no work-around resulting in a patch fix (weeks later) or a fix in a future release (months later).

This:

Error ID: 1867462533-18494 (-412090138)

is what Salesforce term a gack - see the official documentation What Is A Gack?. It is basically a condition that isn't handled well by the platform. While it would be great if Salesforce fixed the platform every time one occurs, in practical terms changing your code to avoid the problem is the more realistic approach.

You could go it alone and make somewhat random changes i.e. review your code and compare with specs and other code and make changes. Or you could engage with Salesforce support so they can lookup their internal logs using the id values in the message and so hopefully narrow down the problem area and guide you to the code to modify; that may take a couple of days. Going that route, it could also turn out to be a platform bug for which there is no work-around resulting in a patch platform fix (weeks later) or a fix in a future platform release (months later).

Source Link
Keith C
  • 127.3k
  • 19
  • 164
  • 343

This:

Error ID: 1867462533-18494 (-412090138)

is what Salesforce term a gack - see the official documentation What Is A Gack?. It is basically a condition that isn't handled well by the platform. While it would be great if Salesforce fixed the platform every time one occurs, in practical terms changing your code to avoid the problem is the more realistic approach.

You could go it alone and make somewhat random changes i.e. review your code and compare with specs and other code and make changes. Or you can engage with Salesforce support so they can lookup their internal logs using the id values in the message and so hopefully narrow down the problem area and guide you to the code to modify; that may take a couple of days. Going that route, it could also turn out to be a platform bug for which there is no work-around resulting in a patch fix (weeks later) or a fix in a future release (months later).