docs/net.corda.core.contracts/TransactionVerificationException/TransactionMissingEncumbranceException

TransactionMissingEncumbranceException

class TransactionMissingEncumbranceException(val txId: SecureHash, val missing: Int, val inOut: TransactionVerificationException.Direction) : TransactionVerificationException

If a state is encumbered (the TransactionState.encumbrance field is set) then its encumbrance must be used as an input to any transaction that uses it. In this way states can be tied together in chains, thus composing logic. Note that encumbrances aren't fully supported by all aspects of the platform at this time so if you use them, you may find transactions created by the platform don't always respect the encumbrance rule.

Constructors

constructor(txId: SecureHash, missing: Int, inOut: TransactionVerificationException.Direction)

Properties

cause

open override val cause: Throwable?

inOut

val inOut: TransactionVerificationException.Direction

whether the issue exists in the input list or output list.

message

open override val message: String?

missing

val missing: Int

the index of the state missing the encumbrance.

originalErrorId

var originalErrorId: Long?

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.