PeerProblem
A problem a peer answered with (RFC 9457): its HTTP status, its Wow code (none for one that is only HTTP's, or a body that is no problem, such as a proxy's), its detail, the command's result when it had a ref, what a retry may do and after how long (retryAfter, its Retry-After), and the aggregate's version it answered: a rejection's, or the current one a state read of a minimum version was answered with (wow.query.min-version-not-reached). A failure the client's transport met itself (no node reached, a connection lost) is one too, of a catalog code, with that failure as its cause.
Properties
The problem's other members, those RFC 9457 and Wow do not name, each by its name.
Whether the node refused the request before handling it, so another node of the peer may take it: a 503 carrying Wow's own code of a node that is shutting down or on standby. A bare 503, or a gateway's, is no proof that nothing ran.
Whether the client sends a command answered so again itself, with its request id: never a
Whether a query answered so is run again: a retry may get past it, a query repeating nothing; but a state read below its minimum version, which the peer already waited for, is the caller's to wait for again (me.ahoo.wow.api.read.MinVersionNotReachedException).
The problem's violations: the fields a request broke.
Functions
The exception of this problem for what was asked: a CommandRejectedException for a command's rejection, else a WowProblemException.