Sequence Errors

If any operation within the sequence experiences an error, then the entire operation is aborted. In this case, your data is left in the same state it would have been in if the sequence had never been run at all — no matter how much of the sequence was run before the error occurred.

Fundamentally, there are two reasons why a sequence might abort:

1. An internal operation results in an exception that is considered a fault. For example, the operation throws a DurabilityException. Also, if there is an internal failure due to message delivery or a networking error.

2. An individual operation returns normally but is unsuccessful as defined by the particular operation. (For example, you attempt to delete a row that does not exist). If this occurs AND you specified true for the abortIfUnsuccessful parameter when the operation was created using TableOperationFactory, then an OperationExecutionException is thrown. This exception contains information about the failed operation.