Sometimes an Apex request gets interrupted/terminated by Force.com. The underlying Apex request contains numerous DML statments (insert into around 13 custom objects) all of which marked at a savepoint. There are no triggers/workflows/formula fields. Also these objects also dont have too many fields. Records are only in few hundreds.

1. What could be possible reasons for DML operation to run long and be interrupted by Force.com?
2. As these are runtime exception, what is the best possible way to handle/react to these exceptions?
3. What troubleshooting will help?

Appreciate any suggestion.

Cheers Siva

Sometimes an Apex request gets interrupted/terminated by Force.com. The underlying Apex request contains numerous DML statments (insert into around 13 custom objects) all of which marked at a savepoint. There are no triggers/workflows/formula fields. Also these objects don't have too many fields. There are only few hundreds of records.

1. What could be possible reasons for DML operation to run long and be interrupted by Force.com?
2. As these are runtime exception, what is the best possible way to handle/react to these exceptions?
3. What troubleshooting will help?

Appreciate any suggestion.