Timeline for Internal Server Error - What's in a GACK?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25, 2017 at 18:31 | vote | accept | dsharrison | ||
| Jul 18, 2017 at 5:19 | comment | added | dsharrison | Yeah, I'll try to dig it up and post it back here if I can. | |
| Jul 18, 2017 at 4:58 | comment | added | ca_peterson | Thanks - is there any chance you can share the case number on that? If it's still happening I'm going to log a bug when I get a chance. | |
| Jul 18, 2017 at 4:57 | comment | added | dsharrison | Thanks for following up on this. With some sweat I was able to get this to Tier 3 support who quickly admitted that despite the stack traces being slightly different I had indeed identified and reproduced a platform regression bug and they provided a workaround in the form of a restructure to the SOQL query. I have not followed up on whether or not this has been fixed since the workaround was easy enough to implement. | |
| Jul 18, 2017 at 4:51 | history | edited | ca_peterson | CC BY-SA 3.0 | added 174 characters in body |
| Jul 18, 2017 at 4:43 | history | answered | ca_peterson | CC BY-SA 3.0 |