+ Start a Discussion
dkorba2k5dkorba2k5 

@future class processing

Is there any way to find out what records have been submitted for @future class processing to make sure that the same record is not being submitted again?

hisrinuhisrinu

unfortunately there is no such option, however if you want to overcome the record locking problem you can make use of FOR UPDATE syntax. Here you might update the same record more than once :(

dkorba2k5dkorba2k5

yeah .. the problem is not occuring within the original trigger loop that's calling out ... it's if the @future class hasn't finished processing and the trigger is called again and does a second call-out.  My alternative is to create an object that stores the id's of the records that have been called-out but not executed and have the @future class remove them from the object.  I was just hoping there was an easier/better way.