Troubleshooting

A workspace or action is missing

Check the signed-in account, selected organization or entity, wallet, and network. Review membership, verification, capability access, and object-specific authority separately.

A public profile, pending application, saved display role, or fee-recipient assignment does not grant mutation rights. Ask the relevant administrator to review the enforced scope.

A saved record is missing from a select

Saved-record selectors list supported records in the current scope. Check that the asset, oracle, market, role, partner, or entity exists, is approved where required, and belongs to the selected context.

Register or approve the missing record through its owning workflow. Do not replace a saved-record selection with a manually typed identifier in an unrelated field.

An amount or duration is invalid

Check the unit beside the control. Asset amounts use the displayed asset and its decimals; percentage controls use percentages; duration controls use hrs., min., and sec..

Review the minimum, maximum, balance, cap, and conditional Unlimited choice. A zero value, an absent value, and an Unlimited selection can have different meanings.

A dependent field disappeared

The product removes inactive decision paths. Select the intended vault type, fee mode, pricing path, access policy, or integration type first, then fill the fields that remain visible.

Review the active path in Workspace Update. Hidden inputs from a previously selected path must not be treated as additional instructions.

A price or NAV is unavailable

Check the selected source, quote asset, decimals, report age, signature quorum, acceptance criteria, and relevant oracle policy. A submitted report may still be awaiting acceptance or activation.

Keep unavailable and stale values distinct from zero. Do not enter a fabricated value to bypass a dependent credit check.

A wallet step was declined

The operation has not completed simply because its review opened. Reopen the operation status and determine whether any preceding approval or transaction already confirmed before retrying.

Keep the original operation and transaction references. Submit only the remaining required action through the supported recovery or retry path.

A transaction confirmed but the screen is unchanged

Trace Chain → Indexer → Projector → Postgres → API → Frontend. Check the operation's completion state and the selected record's freshness.

Reload the same object. If the saved state remains unresolved, retain the transaction reference and report the affected object and operation. Avoid duplicate submissions while completion is pending.

A withdrawal is queued

Inspect available cash, FIFO position, claimable amount, notice, and payout limits. A committed redemption request is not an immediate cash payment.

Use the supported claim action when proceeds become claimable. Do not assume a queue entry can be cancelled or converted back into shares unless that exact action is supported.

A previously available action is now blocked

Permissions, prices, balances, debt, health, facility limits, and timelock state can change between review and execution. Refresh and revalidate the current context before submitting a new action.

A previously calculated maximum or approved draft is not proof that the current action remains executable.

Report an incident

Record the affected workspace, entity or contract reference, current status, operation reference, and observed behavior. Use the relevant incident workflow.

Keep private keys, seed phrases, credentials, reusable signatures, authentication tokens, and unnecessary private operational data out of screenshots, messages, and incident descriptions.