Connection status

The terminal tells you when something stands between you and the exchange: an account that lost its connection, scheduled exchange maintenance, or a break in market data. This page covers each signal, where it shows and what you can do about it.

Account connection

Most of the time the terminal shows no connection status at all. A connected account shows nothing, and neither does one that's still connecting. Only two states show: Reconnecting… and Disconnected.

Idle accounts

Aura disconnects an account from its exchange when nobody has used it for a while, and reconnects it when you come back. The terminal doesn't show this.

Selecting an idle account reconnects it, and so do opening the terminal with it selected, placing an order on it, changing its leverage, Retry and a new API key. While the terminal is open in any tab, visible or hidden, the account selected there stays connected.

An order you place while the account reconnects waits for the connection. If the account isn't connected within 65 seconds of Aura's first attempt, Aura rejects the order with Exchange account could not connect, and the account shows as Disconnected.

Exchanges limit how fast connections can be opened, so when many accounts connect to the same exchange at once, Aura spaces them out and the first attempt can come later. An account with an order waiting goes ahead of accounts without one.

Reconnecting…

If a connected account loses its connection to the exchange and it's still down 15 seconds later, the terminal shows Reconnecting…. Aura is already reconnecting, so there's nothing for you to do.

Reconnecting… shows in the account picker, in the Accounts sheet, above the figures in the Account widget and on the Portfolio page, and on the ticket's submit button, which is disabled until the connection is back.

While the connection is down:

• Aura doesn't cancel your working orders because of the drop.
• A new order placed within 5 seconds of the drop waits for the connection. If the connection isn't back 5 seconds after the drop, the order is rejected with Exchange account disconnected.
• After those 5 seconds, new orders are rejected at once with the same reason, until the connection is back.

Disconnected

When Aura can't connect an account, the account shows Disconnected and an error type. The terminal shows the type, not the exchange's own error.

Where Disconnected shows

• Account picker: a red dot beside the account's name, and the error type in red in the menu.
• Accounts sheet: the account's row shows the dot and the error type, with the button that fixes it.
• Account widget and one account's Portfolio view: a banner above the figures.
• Order ticket: a banner, and the submit button turns into the fix. The close-position dialog shows the same banner.
• Portfolio overview: the account's row shows a red dot and when its balances are from.
• Value figure: a disconnected live account's last balances still count, and the figure dims. Its note says when they're from.

In the Account widget and on the Portfolio page, the banner reads Disconnected · and the error type, then the line from the table. It adds how old the figures are, such as "Balances as of Oct 26, 14:02 UTC." On a live account with open orders, it also says "Your open orders on Exchange stay there and can still fill." It ends with the button and "Need help? Contact support@auraterminal.io". The ticket's banner gives only the error type, its line and the support address.

You can still select a disconnected account to see its last figures. If the account you had selected is no longer available, the terminal picks a working account before a disconnected one.

What you can do

The banner shows one button, the one that can clear the failure. If nothing you do can clear it, it shows only the support address.

Reset paper account opens a dialog titled "Reset account?". It says: "Cancels every open paper order and returns the account's balances to the starting amount. Positions are closed without a trade. This cannot be undone." Click Reset paper account to go ahead. When it's done, a message reads "Paper account reset to its starting balance." See Paper trading.

API key rejected

When the exchange rejects the API key of a live account with open orders, the ticket shows one banner:

"The exchange rejected this account's API key. Update the API keys in Exchange accounts to place orders."

If Aura can't read the key it stored, the banner reads instead:

"The stored API key for this account could not be read. Update the API keys in Exchange accounts to place orders."

The submit button becomes Update API key and opens the key update. Elsewhere, and on the ticket when the account has no open orders, the account shows Disconnected · API key problem. Give the account a new key with the permissions Aura asks for. See Connect an exchange.

Getting help

The support address is support@auraterminal.io. Every Disconnected banner shows it.

Exchange maintenance

Aura warns you about an exchange's scheduled maintenance before it starts. Today the notices come from Coinbase only.

A notice covers the whole exchange, not one market. Aura reads the exchange's published maintenance schedule, so unplanned outages don't get a notice.

The strip

A strip under the top bar, on every page, shows a maintenance window from 24 hours before it starts until it ends. It shows if you have any account on that exchange, Live or Paper. You can't dismiss it.

A window that starts on the current day reads "today" in place of the date. The Details link opens the exchange's own page about the maintenance in a new tab.

The ticket line

From one hour before a window until it ends, the order ticket shows a line above the submit button for the selected account's exchange. The close-position dialog shows the same line.

Note: Maintenance notices never block an order. Submit stays enabled during the warning and the window itself.

The notice follows the exchange's published times. It goes away at the published end, even if the exchange runs over. Its times use the clock you choose in Settings.

Market data

All the widgets in a browser tab share one market-data connection. When it breaks, Aura reconnects on its own, and the widgets show it:

A widget waiting for its first data reads "Connecting to live order book…" (Order Book) or "Awaiting live trades…" (Trades).

If the connection fails to open three times in a row, a widget with no data reads "market data connection failed". The terminal keeps trying once a minute.