Troubleshooting
Use this guide to identify the next safe action during a controlled pilot. Do not share credentials, private keys, seed phrases or raw customer data in tickets or public issues.
Common situations
| Symptom | Safe next step |
|---|---|
| Sign-in or permission is rejected | Confirm the environment and ask the designated administrator to verify the role; do not send the credential |
| Approval cannot proceed | Review the required responsibilities and policy eligibility; do not lower the threshold to force progress |
| Authorization fails | Preserve the request reference and ask the technical owner to review the binding and signing availability |
| Execution outcome is uncertain | Reconcile the external result before retrying |
| Evidence is incomplete | Preserve records and report the missing evidence rather than claiming completion |
| A wallet shows an unexpected network or action | Stop and verify the requested operation before approving |
Requesting support
Provide the environment, product version, request reference, approximate time, visible error category and a redacted screenshot or bounded diagnostic excerpt. Do not include secret configuration or unredacted logs.
Environment-specific diagnostic commands and recovery instructions are supplied to approved operators. Do not delete state, overwrite a live deployment or resend a transaction merely to clear an error.
See Failure recovery and Source and documentation access. If you suspect a vulnerability or a bypass of policy, stop the test and use Responsible disclosure.