Extending Microsoft Dynamics 365 for Operations Cookbook

There's more...

When working with a handler class, also be careful with transaction state. We could update data in a table, for instance, a manually crafted status history table. We can nicely handle any potential exception with a try...catch statement within our handler class, but we can't control what happens when control returns back to the state machine. For example, if we update a history table, but the code fails later on, we could end up with a non-durable transaction if the code handles the exception and continues to commit the transaction.