Transaction Resolution Exception
The node asked a remote peer for the transaction identified by hash because it is a dependency of a transaction being resolved, but the remote peer would not provide it.
Inheritors
Types
Thrown if a transaction specifies a set of parameters that aren't stored locally yet verification is requested. This should never normally happen because before verification comes resolution, and if a peer can't provide a new set of parameters, TransactionResolutionException will have already been thrown beforehand.
Properties
Merkle root of the transaction being resolved, see net.corda.core.transactions.WireTransaction.id
the ID backing getErrorId. If null it will be set dynamically by the flow framework when the exception is handled. This ID is propagated to counterparty flows, even when the FlowException is downgraded to an UnexpectedFlowEndException. This is so the error conditions may be correlated later on.