FAQ and troubleshooting

This page collects common questions and troubleshooting steps for traders using Structure.

Accounts and wallets

Do I need to create a username and password?

No. Structure is wallet‑native. Your identity is your Solana wallet, and you sign in by approving a message in your wallet (Sign‑in with Solana).

I signed in, but I don’t see any strategies or accounts. Is something wrong?

New accounts start empty. After your first sign‑in you must still:

• Create strategies.
• Connect trading accounts.

Use the Getting started guide to walk through these first steps.

Trading accounts and venues

My trading account is stuck in “Pending” or “Confirming”. What should I do?

Check the account’s detail view for instructions. Common issues include:

• A required wallet signature or on‑chain transaction was rejected or not yet signed.
• A DEX delegation or configuration step was not completed.
• For CEX accounts, the provided API keys:
  • Are incorrect.
  • Lack sufficient permissions (for example, can read but not trade).

Try:

1. Restarting the confirmation flow from the trading account page.
2. Ensuring your wallet is connected and unlocked.
3. For CEX accounts, verifying:
   • API key/secret/passphrase values.
   • That the keys have appropriate read and trade permissions (no withdrawals recommended).

If the status moves to Failed, review the error message and correct the underlying issue before retrying.

Can one trading account be used by multiple strategies?

No.

• Each trading account can be assigned to at most one strategy at a time.
• A strategy, however, can use multiple trading accounts.

If you need to reassign an account:

1. Stop the strategy currently using it.
2. Remove the assignment.
3. Assign it to a different strategy.

How do I revoke Structure’s access to a CEX or DEX?

From Structure’s side:

• Remove or disconnect the trading account in the app.

From the venue’s side:

• For CEX accounts:
  • Delete or disable the API keys you previously generated.
• For DEX or blockchain accounts:
  • Revoke or update any delegation or program approvals from your wallet interface.

Revoking at the venue is the ultimate source of truth: even if Structure still has an internal record, it will no longer be able to trade.

Strategies and backtests

Why can’t I start my strategy?

Common reasons a Start action is blocked or fails:

• No confirmed trading accounts are assigned to the strategy.
• The selected revision is not in a stopped state (for example, still baking or already running).
• There is an internal error during the build or deployment process.

Check:

1. The strategy detail page:
   • Confirm at least one confirmed trading account is assigned.
   • Confirm the chosen revision’s status is stopped.
2. Any error message shown in the UI when the start attempt fails.

If the problem persists, contact support with the strategy ID and time of the attempted start.

My strategy shows “baking” for a long time. Is that normal?

baking means Structure is building and preparing your chosen revision for deployment. It should usually transition to running (or occasionally error) within a reasonable time.

If it stays in baking for an unusually long period:

• Check for any alerts or error messages on the strategy detail page.
• If nothing obvious appears, reach out to support with the strategy and revision details.

What does “liquidating” mean for a strategy?

liquidating indicates that a revision has entered an emergency mode, typically because:

• Account health has deteriorated (for example, margin calls or extreme drawdown).
• The system or your logic has triggered a forced de‑risking path.

In this state, the strategy is generally attempting to:

• Close or reduce positions.
• Bring accounts back to safer leverage or margin levels.

You should:

• Review holdings and positions for the affected trading accounts.
• Check venue‑level risk metrics and margin requirements.
• Decide whether to stop the strategy entirely after liquidation completes.

My backtest failed. How can I troubleshoot?

Open the backtest’s detail view and look for an error message. Common causes include:

• Invalid time range:
  • Start or end times outside available data.
  • Start time after end time.
• Insufficient historical data for the requested markets or period.
• Misconfigured arguments (for example, incompatible parameter values).
• Exceeding internal resource or duration limits.

Try:

1. Shortening the time window.
2. Reducing the number of markets or simplifying configuration.

If the error looks internal or persists after reasonable adjustments, contact support with the backtest ID.

Getting more help

If you run into issues not covered here:

• Review the relevant guide (for example, on strategies, trading accounts, or backtesting).
• Gather:
  • The relevant IDs (strategy, backtest, trading account).
  • Timestamps of the problem events.
  • Screenshots of any error messages.
• Contact support through your usual channel, including as much context as possible.

This information helps the team quickly trace what happened in the backend systems and provide a precise answer.