Arcane products have different operating boundaries. Choose the affected product before changing configuration or retrying an operation.
If the result of a state-changing action is unknown, check its current status before submitting it again. A timeout does not prove that the operation failed.

Choose the affected product

Compliance Platform

Diagnose organization access, applications, cases, evidence, and reports.

Privacy Layer for Stellar

Diagnose wallet, private-state, proof, Soroban, delivery, and audit issues.

Privacy Layer for Solana

Diagnose wallet, indexer, proof, relayer, and transaction issues.
Stellar and Solana use separate network-specific implementations. Follow the runbook for the network configured in the affected client deployment.

Determine the scope

Observed impactLikely boundaryNext owner
One user or wallet is affectedIdentity, wallet state, assignment, permission, or local client stateUser or client operator
One application, case, contract, or transaction is affectedProduct configuration, workflow state, approved scope, or transaction stateProduct administrator or integration operator
Several authorized users are affected in one productShared configuration or product serviceDeployment owner or Arcane support
Several products or environments are affectedDeployment or service operationDeployment owner or Arcane support
When several users are affected, preserve evidence before changing shared permissions, endpoints, or configuration. Broad changes can hide the original cause.

Prepare evidence

Collect the minimum information needed to reproduce the issue:
  • UTC date and time;
  • affected product and environment;
  • organization, application, network, contract, case, job, or public transaction identifier, where relevant;
  • exact error message and response status;
  • last confirmed workflow stage;
  • whether another authorized user can reproduce the issue.
Never share access tokens, passwords, recovery phrases, wallet secret keys, wallet signatures used to derive private state, relayer private keys, private audit decoding material, or unredacted private transaction payloads.

Escalate the issue

Use the support channel assigned to your deployment. If you do not know that channel, contact your organization’s Arcane deployment owner and provide the minimum evidence above.

Contact Arcane support

Review the escalation path and evidence requirements.