BTC client posts outbound trackers here
https://github.com/zeta-chain/zeta-node/blob/cb59ddede254806c4469d7909cef0941c88a4c91/zetaclient/chains/bitcoin/signer/signer.go#L221-L228
The error here is ignored, and the outbound gets added to the includedTx map. This map is local to a particular observer.
Since the tracker is never posted, other observers are not aware of this outbound and never try to vote .
This can cause the CCTX to get stuck.
It can be replciated by running the chaos test on develop