--- title: "Combine several conditions in one alert" slug: "combine-technical-conditions" kind: "HELP_ARTICLE" category: "alerts" locale: "en" canonical: "https://help.forecastcity.com/alerts/combine-technical-conditions" published: "2026-09-08T17:58:35.210Z" updated: "2026-10-27T17:05:41.022Z" description: "Combine price, RSI and candlestick pattern conditions in one alert, see why and is checked before or, and group conditions with your own parentheses." --- # Combine several conditions in one alert One condition is often not enough. You may want to know when EURUSD crosses 1.09, but only when RSI or a candlestick pattern backs up the move. Putting several conditions into one alert gives you a single notification when the whole combination is true. ForecastCity makes this simple, fast and accurate. Build the combination in a few clicks. You can also tell or ask AI Trading Assistant in your own voice or in writing to set it up alongside 4CastMachine AI forecasts. The example: EURUSD crosses above 1.09 on 15-minute candles, while RSI is above 55 or the same candle completes a Hammer or a bullish Engulfing. ## Add conditions Every condition you add belongs to the same alert. The alert fires when the whole combination is true, so you get one alert, not one per condition. - Press **\+ Add condition** to add a condition at the end. It starts joined with **and**. - Press `Enter` in a box you type into, such as a price or a period. A new condition appears right below that one, inside the same parentheses. - From the second condition on, each row starts with its own **and** or **or**. Changing it changes that row only. - To delete a condition, move the mouse over its row and press the bin (**Remove**). An alert with more than one condition needs a subscription plan that includes multi-condition alerts. If your subscription plan does not include them, pressing **\+ Add condition** or **Create** opens an upgrade card. ## Read an alert that uses both joins When an alert uses both joins, the editor checks **and** first, then **or**. It works like arithmetic, where you multiply before you add. The editor shows you the result. It draws the parentheses in the rows and in the summary. In the picture below, the RSI row is joined with **or** and the pattern row with **and**. So those two rows go together in parentheses. The alert fires when price crosses above 1.09 on its own, or when RSI is above 55 and a pattern completes. ![Three condition rows where the editor draws parentheses around the two rows joined by and.](https://m.forecastcity.com/t/tnt_forecastcity/media/54/542c9034b3c939437172c14b673b0ba5816cec327a8cd7806be579101a8b52a4.png) The editor puts the two conditions joined by and in parentheses. 1. **or**: this row's join. Each row from the second one has its own join. 2. The parentheses the editor drew around the RSI and pattern rows, because **and** is checked before **or**. 3. **Alert me on EURUSD if:** the summary reads the alert back with the same parentheses. Move the mouse over a row and then over the grey **(i)** to read the same rule in the editor: "and is checked before or, so parentheses show which conditions are checked together. Use ( ) on a row to group it with the next row yourself." ## Put conditions in parentheses yourself Use your own parentheses when you want an **or** to be checked first. 1. Move the mouse over the first condition that should go inside the parentheses. 2. Press **( )** at the right of the row, labeled **Put in parentheses with the next row**. The row and the next one are now in parentheses. On the last row, **( )** pairs it with the row above instead. On a row that opens your own parentheses, the same button reads **Remove parentheses**. Parentheses the editor drew have no button. To change them, change an **and** or an **or**. ## Example: a crossing confirmed by RSI or a candlestick pattern 1. Open EURUSD in 4CM-AI Charts on the **15m** timeframe. New conditions then start on **15m**. 2. Click the lightning icon (**Alerts**) in the top toolbar and press **+**. 3. Build the first condition: choose **Price**, set the timeframe to 15m, choose **crosses above**, and type 1.09. 4. Press **\+ Add condition**. Keep the join on and, then choose **RSI** on 15m with period 14, is above, and 55. 5. Press **\+ Add condition** again. Set the join to or and choose **Candles**. A pattern button appears that reads Pattern… until you choose a pattern. 6. Click **Pattern…**. Under Bullish, tick Hammer and Engulfing, then click outside the list so the button reads **2 patterns**. 7. Read the summary. It puts the crossing and RSI in parentheses, so a Hammer or an Engulfing alone would fire the alert. That is not what you want. 8. Move the mouse over the RSI row and press **( )**. Now the RSI and pattern rows are in parentheses together, so the alert means the crossing, and RSI or a pattern. 9. Open the **Options** tab. Keep Once only for a single alert, or choose Once per bar close to keep the alert running, then press **Create**. ![Three condition rows, the last two in parentheses joined by or.](https://m.forecastcity.com/t/tnt_forecastcity/media/42/42cc5e69f9312be086f450221e5946b432f872293beaa7ea6dd781ef89f5edda.png) With your own parentheses, price must cross 1.09, and RSI or a candlestick pattern must agree. 1. **( )**: puts a row in parentheses with the next row. On this row it reads **Remove parentheses**, because the row opens your own parentheses. 2. **or**: the join inside the parentheses. Either RSI or a pattern is enough. 3. The bin, **Remove**: deletes the condition. ## When does it fire? All three conditions use 15m candles, so the alert checks them each time a 15-minute candle closes. The **crosses above** condition happens at one moment, when a candle closes above 1.09. A pattern also completes at one moment, on the candle that closes it. The **is above** condition stays true while RSI stays above 55. - At 10:15 a 15-minute candle closes at 1.0885. - At 10:30 the next candle closes at 1.0912. Price has crossed 1.09, and RSI is 57 at that close. The alert fires. - Say RSI is only 52 at 10:30. The alert still fires if that candle completes a Hammer or a bullish Engulfing. With neither, nothing happens, and the alert waits for the next crossing of 1.09. With **Once only** the alert then stops. With **Once per bar close** it keeps running and can fire again at a later crossing. ## When the editor refuses two moments A crossing, an entry into a price range and a completed candlestick pattern happen at one moment. Each timeframe is checked on its own, at its own candle close. A touch of a chart line is checked at each price update. A price crossing on 15m and an RSI crossing on 1h, joined with and, can never be true together. That holds even when a 15m candle and a 1h candle close at the same minute. The editor warns that both conditions are moments and cannot be true at the same time. To fix it, join them with or, or change the RSI condition from **crosses above** 50 to **is above** 50. Two moments on the same timeframe are fine. Two candlestick patterns can complete on the same candle. ## Add a 4CM-AI condition A **4CM-AI** forecast condition can share an alert with these conditions. Two rules apply, and the editor names the fix: - Join 4CM-AI conditions to the other conditions with **and**. For **or** between the other conditions, put them in parentheses. Otherwise the editor says "Combine 4CM-AI conditions with the other conditions using and. Put the other conditions in parentheses to use or between them." - Keep 4CM-AI conditions out of parentheses that also hold other conditions, including parentheses the editor draws. Otherwise it says "Keep 4CM-AI conditions out of parentheses that contain other conditions." Rules for several 4CM-AI conditions are in [Combine forecasts from several timeframes in one alert](). ## Good to know - One alert holds up to 10 conditions. An eleventh is refused with "An alert can hold up to 10 conditions. Remove one." - Parentheses can sit inside parentheses only a few levels deep. Past that the editor says "These parentheses nest deeper than alerts support. Remove a pair of parentheses or change an and/or." - Conditions on chart lines take more room. With too many of them the editor says "This alert carries too many chart lines to save. Remove one condition." - Older saved alerts may use n of or weighted as a join, or not to reverse a condition. They keep working. New alerts are built from **and**, **or** and parentheses. ## If it does not fire - Open the alert with **Edit** and read the summary. Its parentheses are the ones the alert uses. - A moment counts only at the candle close where it happens. If the other conditions were false then, the alert waits for the next one. - A combination that is already true when you press **Create** does not fire. It has to become false and then true again. - Check each condition's timeframe. Each one is measured on candles of its own timeframe. ## Related guides - [When does an alert fire? Timeframes and repeats]() - [Create RSI, moving average and ATR alerts]() - [Create candlestick pattern alerts]() - [Combine forecasts from several timeframes in one alert]()