Apex Code Development You need to sign in to do that
Don't have an account?
middleEarth System.UnexpectedException: Failed to enqueue future method
Hi all,
Our code base has not changed since the 16th of May 2014, yet since the latest release (Summer 14) we are now experiencing sporadic @Future Enqueue errors.
"System.UnexpectedException: Failed to enqueue future method"
Is anyone else getting this since Summer 14?
We're on the EU instance - and this stuff started happening on Sunday (the update weekend).
I've tried a "finest" detailed debug log yet that draws a blank since this seems to be thrown from the bowels of sfdc....
For example:
11:53:11.100 (7100242247)|STATEMENT_EXECUTE|[690]
11:53:11.100 (7100252361)|HEAP_ALLOCATE|[690]|Bytes:31
11:53:11.100 (7100269208)|HEAP_ALLOCATE|[690]|Bytes:16
11:53:11.100 (7100285683)|HEAP_ALLOCATE|[690]|Bytes:4
11:53:11.100 (7100583228)|HEAP_ALLOCATE|[690]|Bytes:8
11:53:11.100 (7100686937)|HEAP_ALLOCATE|[690]|Bytes:4
11:53:11.100 (7100714332)|HEAP_ALLOCATE|[690]|Bytes:12
11:53:11.100 (7100898053)|HEAP_ALLOCATE|[690]|Bytes:16
11:53:11.100 (7100937825)|HEAP_ALLOCATE|[690]|Bytes:6
11:53:11.100 (7100997521)|HEAP_ALLOCATE|[EXTERNAL]|Bytes:36
11:53:11.101 (7101014480)|HEAP_ALLOCATE|[EXTERNAL]|Bytes:36
11:53:11.119 (7119196025)|EXCEPTION_THROWN|[690]|System.UnexpectedException: Failed to enqueue future method: MYCLASSNAME:MYFUTUREMETHOD
(MYCLASSNAME & MYFUTUREMETHOD have been renamed to protect the innocent ;-) )
Can anyone from Salesforce comment on this and advise?
Thanks,
Mark
Our code base has not changed since the 16th of May 2014, yet since the latest release (Summer 14) we are now experiencing sporadic @Future Enqueue errors.
"System.UnexpectedException: Failed to enqueue future method"
Is anyone else getting this since Summer 14?
We're on the EU instance - and this stuff started happening on Sunday (the update weekend).
I've tried a "finest" detailed debug log yet that draws a blank since this seems to be thrown from the bowels of sfdc....
For example:
11:53:11.100 (7100242247)|STATEMENT_EXECUTE|[690]
11:53:11.100 (7100252361)|HEAP_ALLOCATE|[690]|Bytes:31
11:53:11.100 (7100269208)|HEAP_ALLOCATE|[690]|Bytes:16
11:53:11.100 (7100285683)|HEAP_ALLOCATE|[690]|Bytes:4
11:53:11.100 (7100583228)|HEAP_ALLOCATE|[690]|Bytes:8
11:53:11.100 (7100686937)|HEAP_ALLOCATE|[690]|Bytes:4
11:53:11.100 (7100714332)|HEAP_ALLOCATE|[690]|Bytes:12
11:53:11.100 (7100898053)|HEAP_ALLOCATE|[690]|Bytes:16
11:53:11.100 (7100937825)|HEAP_ALLOCATE|[690]|Bytes:6
11:53:11.100 (7100997521)|HEAP_ALLOCATE|[EXTERNAL]|Bytes:36
11:53:11.101 (7101014480)|HEAP_ALLOCATE|[EXTERNAL]|Bytes:36
11:53:11.119 (7119196025)|EXCEPTION_THROWN|[690]|System.UnexpectedException: Failed to enqueue future method: MYCLASSNAME:MYFUTUREMETHOD
(MYCLASSNAME & MYFUTUREMETHOD have been renamed to protect the innocent ;-) )
Can anyone from Salesforce comment on this and advise?
Thanks,
Mark
We have a bunch of future methods in our salesforce instance and we have not noticed this issue (yet). Did you raise a support cas with Salesforce?
Anup
You raise a case with them and they issue a stock template response stating to make a post here. (Without reading the case which highlights the fact that I had already posted to here in an attempt to mitigate such a response!).
It's transpired that not all futue methods that are affected - just those with BLOBS as part of the method call (with binary data).
Thanks,
Mark