Explain a backtracked operation in a Tezos manager batch
One signed operation group can contain several manager actions. An explorer that displays only inclusion or the first action can make a failed batch look like a completed payment.
Read every content result
Open the included operation and inspect metadata.operation_result.status for each content in order. The example shows a group in which the middle action fails during application.
contents[0] transaction backtracked
contents[1] transaction failed
contents[2] transaction skipped
The first action was executed then reverted. The second carries the error that interrupted the group. The third was never executed. Inspect nested internal operation results if the failing action invoked another contract.
Reconcile fees separately
Failure during application can still consume fees and advance manager counters for the included group. Reconstruct balance movements from the receipt before resubmitting. A group rejected before inclusion has a different accounting outcome. octez.tezos.com Octez protocol documentation