When editing geodatabase programmatically in short transaction mode (we are working with non-versioned enterprise geodatabase tables), a failed chained operation does not cause the parent operation to be rolled back. Is this an expected behavior? If so, can anyone suggest a solution to this? Thanks!
Yes this is the expected behavior and will also occur in datasets that support undo, the difference of course it that you can undo the parent operation on those and the whole chain goes.
If all you have is simple creates in unversioned data and want to 'undo' them, you could maintain a list of creates via the EditCompletedEvent then delete them when the chained operation fails.