Broker Panel Connections and Automated Execution
A broker connected to TradingView's Trading Panel supports chart trading. That connection does not automatically route Pine strategy trades to the account. TradingView's strategy-automation help page identifies that distinction. [S01]
A recurring practical question is why a manual order works while a strategy produces no broker order. Start by identifying the receiver for the strategy alert. With no external execution route, a simulated trade remains part of the strategy model. Review the webhook setup guide before changing brokerage permissions.
Stock and ETF Execution Routes
Interactive Brokers
AlgoWay lists Interactive Brokers among its destinations. Establish the account connection, instrument identification, quantity and supported order fields. Do not transfer a claim about another broker's fractional or bracket support to this route. [S17]
TradeStation
AlgoWay also lists TradeStation. TradersPost's stock documentation covers broker connections, providing another route to examine alongside AlgoWay. Compare the exact account and instrument, not merely the presence of both names in a platform list. [S17] [S21]
Other documented broker routes
Alpaca provides first-party documentation about stock order eligibility. Its direct API capabilities do not establish that every automation connector exposes those options. Read the broker rule and check that the receiver can transmit the required instruction. [S15]
| Broker or route | Evidence available | Session and order check | Quantity check |
|---|---|---|---|
| IBKR through AlgoWay | Destination listed | Confirm supported orders and account session settings | Instrument identity and share units |
| TradeStation through AlgoWay | Destination listed | Confirm order type and time-in-force | Whole or fractional support for this route |
| TradersPost stock routes, compared with AlgoWay | Stock documentation and AlgoWay destination list | Compare exposed order fields for the same broker | Fractional support needs separate verification |
| Direct Alpaca API | Broker order specification | Extended-hours and bracket restrictions documented | Use product-specific quantity rules |
Trading Sessions and Supported Orders
A signal outside the regular session can encounter an ineligible order type, a queued order or a rejection. Establish which response your broker and route provide. Extended-hours bars on the chart do not enable extended-hours execution.
Alpaca illustrates the distinction: eligible extended-hours orders require an explicit setting, while its documented bracket-order flow does not support extended hours. Verify the complete order combination instead of checking “extended hours” and “brackets” as independent features. [S15]
Consider an alert after the closing bell. The intended behavior might be to place an eligible limit order immediately or wait for the next regular session. Those are different instructions. Record the expected behavior before testing, including expiry of any order left working overnight.
Shares, Fractional Sizes and Short Orders
Ten shares, ten dollars of stock and ten percent of equity are different quantities. The receiver needs a declared sizing interpretation. Fractional holdings at a broker do not establish support for every fractional order type through every connection.
A sell can reduce owned shares or request a short position. Account permissions, buying power and instrument eligibility matter for the latter. Test a close from an existing long separately from a short entry starting flat. A strategy alternating buy and sell can conceal this difference on a historical chart.
Also distinguish transaction quantity from final target position. Reversing ten shares long to ten shares short involves selling twenty shares; a system targeting minus ten can perform the conversion itself. Mixing those meanings creates oversized exposure. The Pine Script guide explains the source side.
Paper Testing and Live Account Differences
Interactive Brokers documents differences between paper and live trading, including simulated execution. Paper testing verifies connectivity and intended order behavior; it cannot establish live queue priority or actual slippage. [S16]
| Paper test | Record | What it establishes |
|---|---|---|
| Regular-session entry | Submitted and filled share quantity | Basic route and sizing |
| Outside-session signal | Status, eligibility and time-in-force | Session behavior |
| Partial exit | Sold quantity and remaining shares | Reduction semantics |
| Protective order | Accepted order and covered exposure | Protection configuration |
| Account reconnection | Authentication and pending orders | Recovery behavior |
Keep timestamps and broker IDs for each case. For a delayed fill, compare acceptance with execution before blaming delivery. A working limit order may simply be waiting for its price. The diagnostic guide separates those stages.
Questions and Answers
Why is my connected broker not executing strategy alerts?
A manual Trading Panel connection does not create a strategy execution route. Confirm the alert, receiver and account instruction separately.
Can my automation trade outside regular hours?
That depends on the exact broker, account, instrument, order type and connector. Test the combination; a chart showing pre-market prices is insufficient evidence.
Does broker support imply fractional-share support?
No. Confirm fractional sizing in both broker documentation and the selected connector's schema, including order-type restrictions.
Does a paper fill predict the live fill price?
No. It verifies a simulated workflow. Live execution introduces actual liquidity and order priority.
Sources & further reading
Official documentation supports the technical claims. Community discussions illustrate user questions, not verified product behavior. Rules and account terms can change.
- S01TradingView: native strategy automation
- S17AlgoWay: platforms, plans and registration
- S21Stock Trading — TradersPost
- S15Alpaca: order capabilities and constraints
- S16IBKR: paper versus live trading