Troubleshooting
Concepts and scope · This page does not establish feature availability.
Reviewed 2026-09-06
A setup guide or command is missing
Section titled “A setup guide or command is missing”The current library explains concepts and evaluation boundaries. It does not yet contain verified setup tutorials or executable API examples. Ask support for the supported path for your release instead of guessing an endpoint or installing a package from an illustrative example.
Provider alerts are absent from a direct account
Section titled “Provider alerts are absent from a direct account”Provider subscriber and direct Individual relationships are separate. Matching wallet addresses do not link identities, permissions, data, or subscriptions. Contact the provider for its subscriber experience; describe a direct Individual issue separately.
A notification seems absent or late
Section titled “A notification seems absent or late”Record the observed event and time, the affected wallet or group, the expected channel, and the result you can actually observe. Confirm the monitoring scope with the Team or provider responsible for it. For separately supplied UserWallets, the delivery route is webhooks only.
Do not treat the absence of a notification as proof that no relevant event occurred. Use the delivery proof model to separate observations from assumptions. Recovery controls depend on the release; support can confirm the available steps.
A report has no data
Section titled “A report has no data”N/A (no data found) means the investigation did not find evidence for that question. It does not establish safety, trustworthiness, or a favorable result.
Report a documentation problem
Section titled “Report a documentation problem”Send support the page URL, the step or statement in question, and the observed result. Do not include private keys, authentication tokens, or wallet recovery phrases. Every page includes its review date and a Markdown download to make the relevant text easy to identify.