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

Privacy Layer for Stellar

Prepare and execute errors, retry, and persisted SDK state.

Privacy Layer for Solana

Solana application example. A network runbook is not published yet.
Stellar and Solana use separate network-specific implementations. Follow the runbook for the network configured in the affected client deployment.

​
Determine the scope

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.