Timeline for Ghost processes / batch processes (NA34 and NA39)
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2020 at 8:11 | history | edited | CommunityBot |
Commonmark migration
|
|
| Apr 13, 2017 at 12:54 | history | edited | CommunityBot |
replaced http://salesforce.stackexchange.com/ with https://salesforce.stackexchange.com/
|
|
| Apr 4, 2017 at 14:40 | history | bounty ended | CommunityBot | ||
| Mar 27, 2017 at 14:48 | comment | added | Phil Hawthorn | Looking at the case notes, I also had access to Apex logs that showed 'First error: connection was cancelled here’ so I guess they were obliged to investigate that in the first instance. | |
| Mar 27, 2017 at 14:45 | comment | added | Eric | Thanks for the info. Any answer right now is good. i am attempting to gather all the information I can before I attempt to submit a case. The only proof I have at the moment is the absence of proof lol. We currently have 3-4 customer reporting this with similar heuristics. the other 400+ customers are not reporting anything (yet). The only common thread is that there is no process running in their orgs at the time and the timestamps in external system do not match with any scenario I can come up with that could cause it | |
| Mar 27, 2017 at 14:42 | history | answered | Phil Hawthorn | CC BY-SA 3.0 |