Connected. Configured. Actually trading?

The green indicator is not the whole story

You have connected a broker, selected a strategy and funded the account. Nothing appears to happen. Is the market closed? Is the strategy waiting? Did the software fail? A single connection indicator cannot answer all three questions, even when it is reporting its own part of the system correctly.

Automated execution has several stages: authenticating the connection, reading the account, loading the selected configuration, receiving a current target, calculating an order and obtaining the broker’s acceptance and fill. A problem at one stage can leave another stage looking healthy.

The useful response is to trace the sequence. Reconnecting everything immediately may replace a visible symptom without explaining its cause. Equally, submitting manual trades to “make it work” can change the account state the software uses for its next calculation.

Confirm the environment and the account

Paper and live environments should be unmistakable. A paper connection can work perfectly while no live trade is expected. Alpaca, for example, documents separate paper and live credentials and endpoints. It also explains that simulation has limits. See Alpaca’s paper-trading documentation.

In SquaredQ, first confirm the broker account shown in MyAlgo and whether the chosen integration supports the environment you intend to use. The documented Public integration is live only; paper or sandbox availability differs across the other supported brokers. Do not assume that a switch supported by one broker exists for every connection.

Next check the permissions for the instruments involved. A funded account can still lack a necessary approval, available buying power or support for the order type. The broker guides explain the connection method and the account-dependent questions to resolve.

A session can require attention after onboarding

Some broker integrations depend on an authenticated session that has a lifecycle. Interactive Brokers documents daily configuration options and a weekly reauthentication cycle for TWS and IB Gateway. A persistent cloud computer does not remove that broker requirement. Read the current IBKR session guidance.

SquaredQ’s documented IBKR path uses the local Gateway or TWS session within the assigned cloud environment. Session health, API settings and the selected account therefore matter alongside the Reader’s own status. The IBKR connection guide provides the starting point.

This is a good example of why “cloud hosted” and “never needs attention” are different claims. Hosting can keep software available independently of your laptop, but it cannot grant permissions or maintain an authentication state that the broker requires you to renew.

Understand the activation boundary

SquaredQ’s documented setup sequence is deliberate: connect and validate the broker, choose the products and allocations, configure Risk Management, review the configuration, then affirmatively activate. A subscription or saved configuration alone is not the final trading authorisation.

That gives you a place to check the account and settings before the software can place unattended orders. After activation, a new approval is not requested for each trade. The strategy determines its underlying targets, while the Reader translates those targets into orders subject to the account’s constraints.

If execution was previously stopped by a risk action, it remains disarmed until the required user action. A later market recovery does not automatically rearm it. Before activating again, inspect the configuration and current broker positions so that the next action is intentional.

No order can be the correct result

A strategy may be between scheduled decision points. The current portfolio may already match its targets closely enough that no additional order is required. A desired quantity may round to zero. A configured capital amount may be insufficient for a particular instrument. Each is a different explanation for the same observation: no new trade.

Ask what event the strategy is waiting for and what account state would require an order. The answer should follow the product’s construction and execution rules. A lack of activity is neither proof of failure nor proof of healthy operation.

For an apparent fault, record the time, environment, product, visible status and relevant broker response. Distinguish an order that was never submitted from one that was rejected, cancelled or only partly filled. That information narrows the investigation far more than a screenshot of an unchanged balance.

How SquaredQ brings the setup into one place

MyAlgo brings broker configuration, product allocation, risk settings and execution controls into the customer workflow. The dedicated Reader performs the account-specific calculations, while operational telemetry helps support investigate connection and execution states. The value is a clearer sequence of checks, not a promise that external brokers will never disconnect.

Use the MyAlgo guide alongside your broker’s current documentation. If a step remains unclear, ask a specific setup question before live activation. A workflow you can explain is easier to operate when the next connection question inevitably appears.