Tezos Stack Exchange is a question and answer site for users, experts, and developers of the Tezos blockchain project. It only takes a minute to sign up.
Sign up to join this community
Applied is self explanatory but the others really arent. The source code gives a bit of clues though; as file apply_results.mli says
[Skipped] ones should always be at the tail, and after a single [Failed]
So in which cases would failed be used over backtracked, and vice-versa? And will we always have guaranteed atomicity on the entire group of transactions in an operation?
The idea is pretty simple:
failed - operations which failed with some particular error (not enough balance, gas limit, etc);backtracked - operations which were successful but reverted due to one of the following operations in the same operation group was failed;skipped - all the operations after the failed one.However, after Babylon update some errors cause the operation to be marked as backtracked, but not failed. For example, when sender can't pay allocation fee.
So, it looks like this:
Operation group:
backtracked
backtracked
backtracked
failed (or backtracked) <-- here is the actual error
skipped
skipped
skipped
And yes, all operations in the same operation group are atomic.
