Operation batches can have both failed/skipped/backtracked transactions and applied reveals
There are cases where an operation group includes a reveal operation after other manager operations. If one of the manager operations fails before the reveal then the every operation in the group should either become backtracked, failed, or skipped. This does not occur for reveals, which will be applied even after a failed operation.
Example: https://tzkt.io/oo3Hr7nKpv6T5iWmK3ibXv6H933cySAaFpYKjTgueSbspVrEGWt
Note that reveal also consumes zero gas units.
Another nuance around reveals is that it does not seem to even matter if it gets the "applied" status. The following are two accounts which have a backtracked or failed reveal that were able to make more transactions without ever making a "applied" reveal operation.
Examples:
- https://tzkt.io/oouyv3HNJz4qEWwR1k8DuCinZGi1z9FfEJnyuGjVjKzt86acGm8
- https://tzkt.io/ooSocfx3xxzDo7eFyGu6ZDR1svzMrbaJtBikQanXXhwrqMuWfGz
Is this behavior expected? It is extremely confusing for developers (in an area which is extremely critical.. knowing if your operation worked on chain) and goes against the idea of "atomic operation groups".