Help

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

Which venues can I connect?

Structure is launching first with Hyperliquid. The app’s trading account flow shows the currently supported venues and the setup steps for each one.

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 account signature or venue authorization step was rejected or not yet completed.
Venue credentials or account details are incorrect.
The connected account lacks the permissions required for strategy execution or account monitoring.

Try:

Restarting the confirmation flow from the trading account page.
Ensuring your wallet is connected and unlocked.
Verifying the venue account details and permission settings shown in the app.

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

Where the venue supports permission scoping, Structure uses the permissions required for strategy execution and account monitoring. Withdrawal and transfer permissions are not part of the launch account model.

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:

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

How do I revoke Structure’s access to a venue account?

From Structure’s side:

Remove or disconnect the trading account in the app.

From the venue’s side:

Revoke or disable the venue authorization, credential, or account permission that allowed Structure to execute through that account.

After access is removed, any live deployment using that account no longer has venue authorization for it. Revoking at the venue is the ultimate source of truth: even if Structure still has an account record, it will no longer be able to execute through that venue account.

Strategies, deployments, and backtest jobs

Why can’t I start a live deployment?

Common reasons a live deployment start action is blocked or fails:

No confirmed trading accounts are assigned to the strategy.
The selected revision has validation or compile errors.
Required Strategy Variable values or deployment settings are missing.
There is an internal error during provisioning.

Check:

The strategy detail page:
- Confirm at least one confirmed trading account is assigned.
- Confirm the selected revision is valid.
- Confirm required Strategy Variable values and deployment settings are complete.
Any error message shown in the UI when the start attempt fails.

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

My deployment shows `provisioning` for a long time. Is that normal?

provisioning means Structure is preparing the selected revision and runtime path. It normally transitions to running or failed.

If it stays in provisioning for an unusually long period:

Check for any alerts or error messages on the deployment detail page.
Confirm the selected revision, connected account, Strategy Variable values, and deployment settings.
If nothing obvious appears, contact support with the strategy, revision, deployment, and connected account details.

What should I do if a live deployment health warning appears?

A live deployment health warning needs immediate review.

Check:

The connected account’s balances, positions, and venue health.
Recent order activity and fills.
Deployment logs and errors.
Strategy behavior and target positions.

Use deployment controls to stop the deployment when appropriate. Manage open positions at the venue if the situation requires direct venue action.

My backtest job failed. How can I troubleshoot?

Open the backtest job 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 selected venue and instrument.
Missing or invalid Strategy Variable values.
Starting balances or simulator settings that are incompatible with the selected revision.
Exceeding internal resource or duration limits.