Deployed

After an algo is backtested, users can take their algos live in the exchange for paper trading, auto trading orthey can chose to get actionable alerts based on the entry and exit conditions in their algo.

You can have up to 25, 50, and 100 live deployments in basic, premium and ultimate plan respectively live.

The moment you click on confirm, the algos gets deployed and you are moved to the Notification, Auto or Paper trading section, depending upon the deployment type selected.

There are 3 different States of an algo

• Waiting
• Entered
• Stopped

Waiting

Indicates the number of algos you have deployed and the Streak bots start tracking for signals. You can have as many as 25 live algos in the waiting and entered section combined for basic plan.

The moment an algo ENTRY criteria is met a Blue or an Orange dot appears and starts blinking continuously.

• Blue dot - Buy (Entry buy) condition has met
• Orange dot - Sell (Entry Sell) condition has met

The moment you click on the blinking dot an order window is shown. You will have to click on the order window to enter the position.

Now, if the order is completed then the algo automatically moves to Entered or if the order gets rejected due to some issue (eg: margin not available), the algo moves to the stopped section.

Entered

Algo in entered state means you have a position open and this position has the SL and TP price mentioned

The moment your TP or SL gets hit you will be notified with the blinking dots

• Red - Stop loss
• Green - Target profit
• Blue dot - Buy (Entry buy or exit condition buy)
• Orange - Sell (Entry or exit condition)

If your algo has 2 or more cycles associated with it. The algo waits in Entered after completing the first cycle.

Stopped

An algo can move to stopped state if you have

• Completed the algo cycle
• Algo was manually stopped
• Algo gets terminated or force stopped (eg. Order rejected)

Redeploy algo

You can always Redeploy a stopped algo anytime and it will move to Waiting state in the deployed section.

Orderlog

You can view the complete details of algo stages including signal generation time by clicking on orderlog on the deployed page.

Algo cycle

Algo Cycle, the entry followed by a respective exit of an algo is algo cycle.

Once an algo is deployed, the stocks are periodically tracked based on the conditions in the algo. The periodicity with which the market is tracked is the same as the candle interval selected by the user while backtesting the algo and shown in the algo summary before deployment. An algo's ideal life cycle and the tree of events that can occur during an algo's life cycle, called an "algo cycle", is explained below:

1. Waits for the first entry event as per the entry condition in the deployed algo.
2. Once the entry event occurs, an entry signal (buy/sell) is triggered and an actionable alert is sent to the user (deployed as Notification).
3. The user can choose to act on the alert by clicking buy/sell or choose to ignore the alert and cancel it (canceling will terminate the algo).
4. If the user has clicked on buy/sell in the alert, a market order is sent to the respective exchange.
5. The order will either be successfully placed by the exchange or it might get rejected due to reasons such as insufficient capital. If the order gets rejected by the exchange, the algo gets terminated.
6. After the successful placement of an order, the algo continues to track the stock waiting for the exit signal (SL or TP) or exit condition. Based on the entry price and the SL and TP percentages entered by the user, the SL and TP prices are calculated which are displayed to the user.
7. When the SL/TP price occurs or if the exit condition is met, whichever occurs first, an actionable notification is sent to the user again. The user has to act on it by clicking buy/sell or choose to ignore the alert and cancel it (cancel will terminate the algo).
8. If the user has clicked on buy/sell in the alert, a market order is sent to the exchange and the algo's cycle is then complete.

In case of Auto trading, the user will not be prompted with actionable notification, orders will be automatically to the exchange.

Points to remember

1. The "algo cycle" sequence defined above is an ideal sequence and is subject to market conditions and user behavior. Based on the user's action or market conditions, the sequence might not completely occur in the same way as it is intended to, since this sequence may have been interrupted due to various reasons such as the user stopping the algo, order rejection by the exchange, network lag, network error, etc.
2. If you select 1 cycle then after 1 entry and the respective entry the algo moves to the completed state and is stopped. The maximum number of cycles per deployment is 5.

3. Margins are not blocked till the user acts on the actionable alerts (buy/sell) and the order is sent to the exchange. Margins if any are blocked by your respective exchange and not Streak.

4. The algo can be stopped by the user at any time in the life cycle of the algo by clicking on the "Stop" button. If the algo has not entered a position, it will be directly stopped otherwise the user will be presented with an option to either stop the algo by keeping the positions open or to exit positions at the market and stop the algo. The algo will no longer be tracked and no further alerts will be sent to the user for the respective algo.

5. In cases where the user stops the algo and chooses to keep positions open, the responsibility of closing any and all positions is solely on the user, and the user will get no alerts for that deployed instrument once the algo is stopped.
6. All actionable order alerts sent to the user can be used only once and will be active for only 5 minutes after which the alert expires in the alerts/ notification section. However, the alerts can be acted by clicking on the take action button to enter the algo.
7. All actionable alert orders are market orders (can be changed to Limit) and users can expect price variation from the price at which the alert was triggered to the price at which the order is placed. This is called Slippage. The slippage for ill - liquid stocks is usually high.
8. If the user's order is rejected due to various reasons such as shortage of funds, no liquidity in the market, etc, the algo will be stopped and no further alerts will be sent for that algo. This is done in order to avoid unnecessary tracking of instruments where the order placement failed. However, the user can deploy the algo again and take action on any new alerts that get generated.
9. Target profit orders are not placed with the entry order. The algo tracks the stock for the stop loss and take profit prices only after entering a position. Once the take profit price is met, an actionable alert is sent to the user and once the user confirms the order, the exit market order is placed and the position is closed.

DISCLAIMER

• Once a signal is generated, we try to send this signal to the user's device over the internet. Alert delivery is subject to network conditions of the user, internet services and technical issues.
• Accurate and complete real-time price data is critical for the success of algorithmic trading. Our service providers or systems that provide data could experience failures, errors, lag, and latency, which could result in missing, incorrect, or stale market data leading to no/wrong signals (alert) while triggering an alert.
• By using this service, the user acknowledges they understand that the alerts' delivery is dependent on many factors such as the internet connection of the user, location, time of the day, server load, data availability, etc.
• We reccomend users to be logged in to streak.world, keep it open in their browser and maintain an uninterrupted fast internet connection to their devices to see the best alerts delivery.
• Streak relies on third-party services for market data, eg: ticks, OHLCV, etc. If these services are down due to unforeseen circumstances or experience a downtime due to various technical/non-technical issues, Streak might not be able to generate and deliver the actionable alerts.
• All actionable order alerts are read-only market order alerts, where with a single click the user can send the order to the exchange. The actionable order alerts are made read-only in order to obtain consistency in the deployed and backtest results and to avoid any drastic increase in risk.
• Upon clicking on BUY/SELL on the order window, based on users' network speed, network latency can be experienced, and any rapid clicks on the BUY/SELL button through the same or different windows can lead to multiple orders placements. Users take full responsibility on making sure the actions on the notifications are their own actions and are fully aware of their positions and algo status when on the BUY/SELL button.