The message payload is empty, making the message invalid. Ensure that a non-empty payload is set on the outgoing message.
Failure to protobuf encode the message. This is not recoverable and needs further investigation.
Could not determine the origin of the fault. Best to check connectivity and try again
Failure to find a peer with suitable protocols. This may due to a connection issue.
Mitigation can be: retrying after a given time period, display connectivity issue
to user or listening for peer:connected:bootstrap or peer:connected:peer-exchange
on the connection manager before retrying.
The remote peer did not behave as expected. Mitigation for NO_PEER_AVAILABLE
or DECODE_FAILED can be used.
The remote peer rejected the message. Information provided by the remote peer
is logged. Review message validity, or mitigation for NO_PEER_AVAILABLE
or DECODE_FAILED can be used.
The protocol request timed out without a response. This may be due to a connection issue. Mitigation can be: retrying after a given time period
The message size is above the maximum message size allowed on the Waku Network. Compressing the message or using an alternative strategy for large messages is recommended.
The PubsubTopic passed to the send function is not configured on the Waku node. Please ensure that the PubsubTopic is used when initializing the Waku node.
Generated using TypeDoc
Failure to protobuf decode the message. May be due to a remote peer issue, ensuring that messages are sent via several peer enable mitigation of this error.