Complete reference

MAGIC ENTRY / RED CODES

Notifications.
Every color explained.

What each message means, why it appears and what to do next. Exact theme colors and previews below the top menu.

107 messages and templates6 interface themes
Advisor previewGraphite
Fixed Lots1.00
BUYSELL
GUARD
FILLED
Success#84B99B
Preview themeChanges these previews only. Advisor settings stay the same.

Event type changes the border and status dot. The selected theme supplies a shared background and text color. Monochrome uses shades of gray for all four types.

Complete reference

All messages
Type
Action
Quick searches:
Showing 107 of 107 messages and templates

01Entry and execution

From Buy / Sell to a confirmed result.

13
MessageBorder colorWhen, why and what to do
Warning#D8B36A
A market request is being sent, including Fixed Lots Buy / Sell.

Why: The advisor is passing the confirmed entry request to the broker; execution is not confirmed yet.

What to do: Wait for the result; do not press Buy / Sell again.

Operation phase
Warning#D8B36A
A pending-order request is being sent.

Why: The advisor is sending a pending order for the selected entry price.

What to do: Wait for the response; do not submit another order.

Operation phase
Warning#D8B36A
The advisor is waiting for the broker after sending the request.

Why: The response and order data do not arrive together, so there is not enough confirmation yet.

What to do: Wait for the broker; do not repeat the request.

Operation phase
Warning#D8B36A
The advisor is checking orders, deals and positions.

Why: The initial response is not enough for a final conclusion, so actual trading state is checked.

What to do: Wait for reconciliation; do not duplicate the entry.

Operation phase
Success#84B99B
Placement of the current order is confirmed.

Why: The broker response or subsequent reconciliation confirmed the corresponding order.

What to do: Check the placed order in the order list.

Operation phase
Success#84B99B
Execution of the current request is confirmed.

Why: The broker response or trading records confirmed the fill.

What to do: Check the actual volume and settings of the open position.

Operation phase
Warning#D8B36A
The current request was filled partially.

Why: The filled volume is smaller than requested, so this is not a full fill.

What to do: Check the filled volume and remaining request; do not duplicate the original full volume.

Operation phase
Error / block#D99A92
The current request was rejected.

Why: The result contains a rejection; its exact cause depends on the broker code and comment.

What to do: Read the rejection code and comment; check orders and positions before retrying.

Operation phase
Error / block#D99A92
The request was not sent.

Why: Preparation or a submission safeguard stopped it before sending it to the broker.

What to do: Resolve the stated cause and start a new entry.

Operation phase
Error / block#D99A92
The entry result is unknown and another entry is blocked.

Why: The response and trading data do not establish a definite result; the block prevents a duplicate entry.

What to do: Check positions, orders and history first; unlock only after establishing the result.

Until the state is resolved
Error / block#D99A92
A first click was made and a second unlock confirmation is expected.

Why: Manual release of the uncertain state requires two user confirmations.

What to do: Before the second click, check positions, orders and history and establish the previous entry result.

Until the state is resolved
Info#52606E
The user confirmed manual unlock.

Why: The confirmation releases the interface block but does not cancel an already sent request.

What to do: Check the previous request before a new entry: unlocking does not cancel it.

Operation phase
Internal
Warning#D8B36A
An internal fallback appears when no completion result is recognized.

Why: The completion code does not match a known result, so a fallback label is shown.

What to do: Check positions, orders and the log; NONE does not confirm a fill.

Operation phase

02Placing levels

Hints while setting or moving price levels.

19
MessageBorder colorWhen, why and what to do
By volume#52606EWithout a calculation
Market entry placement is active.

Why: Market mode is enabled and the advisor is waiting for chart placement to finish.

What to do: Check SL and volume, then finish placement; Esc cancels.

Until complete / Esc
By volume#52606EWithout a calculation
SL or the pending entry price is being set.

Why: Limit mode is enabled and the advisor is waiting for a stop or entry price.

What to do: Check SL, Entry and volume; finish placement or cancel with Esc.

Until complete / Esc
Info#52606E
The main stop-loss is being moved.

Why: SL editing is selected and the new price is still in placement mode.

What to do: Select a valid SL price and confirm; Esc cancels.

Until complete / Esc
Info#52606E
A partial stop-loss is being moved.

Why: The selected stop applies to part of the volume rather than the whole position.

What to do: Select the partial SL price and confirm; Esc cancels.

Until complete / Esc
Info#52606E
The main take-profit is being moved.

Why: Main TP editing is selected and the advisor is waiting for price confirmation.

What to do: Select a valid main TP price and confirm; Esc cancels.

Until complete / Esc
Info#52606E
A partial take-profit is being moved.

Why: The selected take-profit applies to a portion of the volume.

What to do: Select the partial TP price and confirm; Esc cancels.

Until complete / Esc
Info#52606E
The breakeven trigger is being set or moved.

Why: This level sets the condition for moving the stop to breakeven.

What to do: Set and confirm the BE trigger price; Esc cancels.

Until complete / Esc
Info#52606E
The breakeven offset is being adjusted.

Why: The offset sets the protective stop relative to the breakeven reference.

What to do: Set and confirm the stop position after BE activates; Esc cancels.

Until complete / Esc
Info#52606E
The SL trailing start is being set.

Why: The start defines when stop-loss trailing begins.

What to do: Set the SL trailing start; confirm or cancel with Esc.

Until complete / Esc
Info#52606E
The SL trailing gap is being set.

Why: The gap defines the stop distance from the price followed by trailing.

What to do: Set the SL trailing gap; confirm or cancel with Esc.

Until complete / Esc
Info#52606E
The TP trailing start is being set.

Why: The start defines when take-profit trailing begins.

What to do: Set the TP trailing start; confirm or cancel with Esc.

Until complete / Esc
Info#52606E
The TP trailing gap is being set.

Why: The gap defines the take-profit distance from the price followed by trailing.

What to do: Set the TP trailing gap; confirm or cancel with Esc.

Until complete / Esc
Info#52606E
The order entry price is being moved.

Why: A new order price is selected and must pass validation before application.

What to do: Check the new Entry, SL and TP before confirming; Esc cancels.

Until complete / Esc
Info#52606E
A Pending trigger is being placed.

Why: This level defines the activation condition for the Pending scenario.

What to do: Select and confirm the Pending trigger price; Esc cancels.

Until complete / Esc
Info#52606E
SL is being placed for a Pending scenario.

Why: The protective stop of the future Pending entry is being configured.

What to do: Select and confirm the Pending SL price; Esc cancels.

Until complete / Esc
Info#52606E
The Pending entry price is being placed.

Why: The future entry price of the Pending scenario is being configured.

What to do: Select and confirm the Pending Entry price; Esc cancels.

Until complete / Esc
Info#52606E
A cancellation level is being placed.

Why: This level sets the condition for cancelling the corresponding order or scenario.

What to do: Select and confirm the cancellation price; Esc cancels placement.

Until complete / Esc
Info#52606E
A Pending level is being moved.

Why: An existing Pending scenario level is selected for editing.

What to do: Set the new position of the selected Pending level; Esc cancels.

Until complete / Esc
By volume#52606EWithout a calculation
Several placement actions are active.

Why: More than one placement mode is active, so Esc cancels them together.

What to do: Finish the required placements; Esc cancels all active actions.

Until complete / Esc

03Volume and margin

Volume calculations in the Market / Limit preview.

5
MessageBorder colorWhen, why and what to do
Success#84B99B
The calculated volume is valid.

Why: The calculation produced valid positive volume without a margin reduction.

What to do: Check the calculated volume against your settings before confirming entry.

Until complete / Esc
Warning#D8B36A
Volume was reduced because free margin was insufficient.

Why: The original volume exceeds available margin, but a smaller volume is still possible.

What to do: Check the reduced volume and free margin before confirming entry.

Until complete / Esc
Warning#D8B36A
The preview shows the maximum volume available by margin.

Why: Limit margin calculation is enabled and reduces the original volume to the available amount.

What to do: Check free margin, final volume and CALC_LIMIT_MARGIN.

Until complete / Esc
Error / block#D99A92
Margin is insufficient even for minimum volume.

Why: After the margin check, available volume is below the symbol minimum lot.

What to do: Check free margin and the symbol minimum lot; do not confirm entry yet.

Until complete / Esc
Error / block#D99A92
The symbol volume limit was reached.

Why: Accounted volume plus the new request reaches or exceeds the symbol volume limit.

What to do: Check the symbol volume limit and the positions and orders already counted.

Until complete / Esc

04Close Now

Selecting a closing portion and checking its result.

3
MessageBorder colorWhen, why and what to do
Info#52606E
Closing selection shows volume and estimated monetary result.

Why: You are selecting a position portion; the amount uses current data and is an estimate.

What to do: Check the percentage, volume and remainder before confirming the close.

About 3 seconds
Success#84B99B
Closing is confirmed and the closed volume and remainder are shown.

Why: The trading result confirmed the stated closed volume and the remaining position was updated.

What to do: Check the remaining position; do not close the previous volume again.

About 3 seconds
Error / block#D99A92
Closing was not confirmed as successful.

Why: The close returned an unsuccessful result; ret and its description identify the cause.

What to do: Check ret, the log and actual remaining volume before another attempt.

About 3 seconds

05Market and permissions

Terminal, account and broker messages.

13
MessageBorder colorWhen, why and what to do
Error / block#D99A92
Algorithmic trading is disabled in the terminal.

Why: The terminal-wide algorithmic-trading permission is off.

What to do: Enable Algo Trading in the terminal if you want to allow the advisor to trade.

About 5 seconds
Error / block#D99A92
Trading is not enabled for this advisor.

Why: Algorithmic-trading permission is off for this advisor instance.

What to do: Enable Algo Trading in the advisor properties if you want it to operate.

About 5 seconds
Error / block#D99A92
The account does not have trading permission.

Why: The terminal reports that trading is not allowed on the current account.

What to do: Check account trading permissions with the broker.

About 5 seconds
Error / block#D99A92
The account does not allow Expert Advisor trading.

Why: The account blocks operations submitted by an Expert Advisor.

What to do: Ask the broker whether Expert Advisors are permitted on this account.

About 5 seconds
Error / block#D99A92
New symbol trades are restricted, close-only or their status is unavailable.

Why: The symbol is not in full trading mode or the advisor could not read that mode.

What to do: Check the symbol name and mode; ask the broker whether new entries are available.

About 5 seconds
Error / block#D99A92
The broker rejected the request because the market is closed.

Why: The server returned the market-closed code, related to the symbol trading session.

What to do: Check the symbol trading schedule and wait for the session to open.

About 5 seconds
Error / block#D99A92
The broker server disabled algorithmic trading.

Why: The server response reports an automatic-trading prohibition on its side.

What to do: Ask broker support to check permission for Expert Advisor trading.

About 5 seconds
Error / block#D99A92
The terminal disabled algorithmic trading for this request.

Why: The request response identifies an algorithmic-trading prohibition on the terminal side.

What to do: Check terminal Algo Trading and trading permission in the advisor properties.

About 5 seconds
Error / block#D99A92
The broker disabled the trading operation.

Why: The server returned a general prohibition whose details depend on the account or symbol.

What to do: Check account and symbol trading permissions; contact the broker about restrictions.

About 5 seconds
Error / block#D99A92
Funds or margin are insufficient for the request.

Why: The trading result reports insufficient available collateral for the operation.

What to do: Check free margin and request volume before trying again.

About 5 seconds
Error / block#D99A92
The request failed without a specific trading result code.

Why: The terminal returned submission error 4756 without a result code, so this response gives no more precise cause.

What to do: Check the log, connection, orders and positions before resubmitting.

About 5 seconds
Special case
Error / block#D99A92
A post-send message reports volume reduced by margin.

Why: The calculation capped volume by available margin; the display channel gives this message its error color.

What to do: Check actual order or position volume; this message does not require another entry.

About 5 seconds
Error / block#D99A92
Other pending orders also use the available volume or margin.

Why: The margin reduction coincided with other pending orders on the symbol, so their combined fill is not guaranteed.

What to do: Check all symbol pending orders and the margin needed if they execute.

About 5 seconds

06Entry protection

Pre-send checks and ownership safeguards.

13
MessageBorder colorWhen, why and what to do
Error / block#D99A92
Fixed Lots volume failed validation.

Why: The lot amount failed normalization or the symbol volume checks.

What to do: Check Fixed Lots for a positive value and the symbol minimum, maximum and lot step.

About 5 seconds
Error / block#D99A92
The advisor could not safely prepare and record submission.

Why: Recording the operation or passing the entry-start safeguard failed.

What to do: Check the log and advisor readiness; start a new entry after resolving the rejection.

About 5 seconds
Error / block#D99A92
Placement was cancelled because account context changed.

Why: The current account no longer matches the one captured when placement began.

What to do: Check the selected account and restart placement after quotes update.

About 5 seconds
Error / block#D99A92
Quote sources disagree with the current account context.

Why: The checks found incompatible current quote sources and account context.

What to do: Wait for consistent fresh quotes; check the account and server connection.

About 5 seconds
Error / block#D99A92
A new placement is needed after the account changed.

Why: Captured settings belong to the previous account and cannot be reused for a new entry.

What to do: Start a new entry on the intended account and check its parameters again.

About 5 seconds
Error / block#D99A92
OrderCheck rejected the request without an explanatory comment.

Why: The prepared request failed the pre-send OrderCheck and no comment explains it.

What to do: Check request parameters and the OrderCheck log before trying again.

About 5 seconds
Error / block#D99A92
A connection, permission, symbol, quote, execution or OrderCheck test failed.

Why: One pre-send check did not pass; the specific condition follows the colon.

What to do: Read and resolve the reason after the colon before a new entry.

About 5 seconds
Error / block#D99A92
Another protected operation is active on this symbol.

Why: The safeguard prevents overlapping symbol operations until the previous one completes.

What to do: Wait for the current symbol operation to finish; do not start a parallel one.

About 5 seconds
Error / block#D99A92
The uncertain entry could not be registered for symbol coordination.

Why: Recording the symbol protection state is unconfirmed, so entry cannot safely continue.

What to do: Check positions, orders, history and the log; do not repeat entry until its result is known.

About 5 seconds
Error / block#D99A92
Advisor instances have an ownership conflict.

Why: Records disagree about which instance controls the trading state.

What to do: Resolve the instance ownership conflict and reattach the advisor to the chart.

About 5 seconds
Error / block#D99A92
Ownership synchronization has not finished.

Why: The advisor is still restoring or coordinating control, so mutations are temporarily blocked.

What to do: Wait for synchronization; check the log if the message recurs.

About 5 seconds
Error / block#D99A92
Placement cannot finalize because chart visuals are unavailable.

Why: The visual layer is not ready to confirm selected chart levels reliably.

What to do: Wait for chart visuals to recover and check levels before confirming again.

About 5 seconds
Error / block#D99A92
The trading layer supplied its own pre-send failure description.

Why: Request preparation failed before sending; the failing check provides the text.

What to do: Read the failure description and log; retry only after resolving the cause.

About 5 seconds

07SL, TP, BE and Entry

Level validation, protection and saved settings.

17
MessageBorder colorWhen, why and what to do
Error / block#D99A92
The breakeven change could not be saved.

Why: The BE state change was not confirmed, so the new setting is not considered reliably stored.

What to do: Check current BE settings and the log; do not assume the new value was saved.

About 5 seconds
Error / block#D99A92
Settings transfer to a position after replacement fill is unconfirmed.

Why: After a replacement order filled, transfer of its settings to the position was not confirmed.

What to do: Compare actual position settings with the intended ones, especially SL, TP and BE.

About 5 seconds
Error / block#D99A92
Compact mode reports insufficient volume for another partial TP.

Why: There is not enough remaining volume for a new partial TP and the main TP minimum remainder.

What to do: Check position volume, existing TP portions and the symbol minimum lot.

About 5 seconds
Error / block#D99A92
Normal mode requires minimum volume to remain for the main TP.

Why: Another partial cannot reduce the main TP remainder below the symbol minimum lot.

What to do: Check volume distribution across partial TPs and the main TP minimum remainder.

About 5 seconds
Error / block#D99A92
Position state is unavailable for a partial TP change.

Why: The advisor could not obtain current position state needed to modify a partial TP safely.

What to do: Wait for the position to update and check that it exists; inspect the log if this recurs.

About 5 seconds
Error / block#D99A92
A main or partial TP price failed validation.

Why: The proposed TP price is invalid; the reason names the specific restriction.

What to do: Read the reason and check TP price, trade direction and adjacent levels.

About 5 seconds
Error / block#D99A92
Automatic TP was not set.

Why: Automatic TP preparation or application failed; details follow the colon.

What to do: Check the reason, automatic TP settings and current position protection.

About 5 seconds
Error / block#D99A92
State saving for automatic TP is unconfirmed.

Why: There is no confirmation that the position settings needed for automatic TP were recorded.

What to do: Compare actual levels and saved settings before applying again.

About 5 seconds
Error / block#D99A92
The automatic TP plan did not finish completely.

Why: Some TP steps were performed or recovered, but the entire plan did not complete successfully.

What to do: Check existing TP levels and their volumes before applying the plan again.

About 5 seconds
Error / block#D99A92
The automatic TP result could not be confirmed.

Why: Available evidence does not establish the final automatic TP application result.

What to do: Wait for reconciliation and check actual TP levels before applying the plan again.

About 5 seconds
Error / block#D99A92
Default TP / BE application did not finish after entry.

Why: A protection step failed, so the complete TP / BE set is not considered applied.

What to do: Check the new position SL, TP and BE and the failure explanation.

About 5 seconds
Special case
Error / block#D99A92
The partial TP was saved with a nonempty explanation.

Why: Saving returned additional text and this display path sends such explanations through the error channel.

What to do: Check the saved partial TP and explanation; do not add the same partial again.

About 5 seconds
Error / block#D99A92
A partial TP change could not be applied or saved.

Why: Validation, application or saving did not complete successfully; the reason gives the exact condition.

What to do: Check the reason, partial price and volume, then compare actual levels.

About 5 seconds
Error / block#D99A92
The entry-replacement pre-check rejected the change.

Why: The replacement request failed validation before the original order was deleted.

What to do: Correct replacement parameters; verify the original order still exists before retrying.

About 5 seconds
Error / block#D99A92
Replacement state is unconfirmed and settings are retained.

Why: Deleting the original order is unconfirmed and its former identity cannot be confirmed either.

What to do: Check orders, positions and history; do not resubmit the replacement until its result is known.

About 5 seconds
Error / block#D99A92
Entry replacement was interrupted by ownership protection; settings are retained.

Why: After deletion of the original order, ownership protection blocked sending the replacement.

What to do: Check orders, positions and retained settings after synchronization finishes.

About 5 seconds
Error / block#D99A92
Entry replacement is not confirmed and settings are retained.

Why: The replacement submission did not receive an accepted creation confirmation.

What to do: Check for a replacement order or position and inspect the log before retrying.

About 5 seconds

08Groups and trailing

Shared protection and consistent group members.

24
MessageBorder colorWhen, why and what to do
Error / block#D99A92
A shared partial level or member data was not found.

Why: The selected partial has no confirmed shared link between group members.

What to do: Set the shared partial level first, then select the group again.

About 5 seconds
Error / block#D99A92
The partial level is not linked to the other members.

Why: The selected partial is still individual rather than shared across positions.

What to do: Make the selected partial shared across the group first.

About 5 seconds
Error / block#D99A92
The link between partial levels was not saved.

Why: The advisor did not confirm recording the partial-level correspondence between positions.

What to do: Select the group again and check partial links; inspect the log if this recurs.

About 5 seconds
Error / block#D99A92
The selected group membership or identity changed.

Why: The captured group no longer matches current positions or their identities.

What to do: Select the current group again and check its members before editing.

About 5 seconds
Error / block#D99A92
A member is not ready for a group operation.

Why: At least one member lacks ready state for a safe group change.

What to do: Wait for all members to update; check the positions and log.

About 5 seconds
Error / block#D99A92
The group change was not saved for every position.

Why: Only the stated number of members were saved successfully; the others need verification.

What to do: Check each member settings and identify positions without confirmed saving.

About 5 seconds
Error / block#D99A92
A shared BE offset is being changed before shared BE is enabled.

Why: The shared BE trigger is not enabled and an offset requires that trigger.

What to do: Set and enable the shared BE trigger before changing its offset.

About 5 seconds
Error / block#D99A92
The shared trailing gap has no start level.

Why: The gap depends on a start level that has not been set.

What to do: Set the shared start for the selected trailing type before its gap.

About 5 seconds
Error / block#D99A92
A member state could not be read while preparing shared protection.

Why: Data for at least one position could not be obtained for the shared plan.

What to do: Check that every position exists and is ready; select the group again after it updates.

About 5 seconds
Error / block#D99A92
The shared plan does not fit every position.

Why: Entry prices, volumes or level restrictions prevent the same plan from fitting all members.

What to do: Compare member entries, volumes and levels; the shared plan must fit each member.

About 5 seconds
Error / block#D99A92
Shared protection does not fit the proposed entry or volume.

Why: The new entry or volume is incompatible with the selected shared protection plan.

What to do: Check the proposed Entry and volume against shared protection before confirming.

About 5 seconds
Error / block#D99A92
Shared protection could not be saved for a position.

Why: Recording the member shared protection plan was not confirmed.

What to do: Check the stated position protection and saved settings, then inspect the log.

About 5 seconds
Error / block#D99A92
Group BE rebasing was not saved after membership changed.

Why: The new shared BE reference was not reliably stored after the group changed.

What to do: Check shared BE and each position BE after membership changes.

About 5 seconds
Error / block#D99A92
The previous grouped partial TP save is still unconfirmed.

Why: Another change is blocked until the previous group partial-save result is confirmed.

What to do: Wait for the prior save confirmation and check partial TPs before editing again.

About 5 seconds
Error / block#D99A92
Shared levels changed after placement began.

Why: Protection settings changed during the gesture, so its price refers to an outdated plan.

What to do: Select the group again and start placement using its current levels.

About 5 seconds
Error / block#D99A92
A member has insufficient volume for another partial SL / TP.

Why: At least one member lacks enough volume for a new portion and the required remainder.

What to do: Check each member volume and its existing SL / TP portions.

About 5 seconds
Error / block#D99A92
A shared TP or partial TP price failed a member check.

Why: The common TP price is invalid for one member; the restriction follows the colon.

What to do: Read the reason and compare shared TP against every member permitted levels.

About 5 seconds
Error / block#D99A92
Member state is unavailable for a partial TP change.

Why: Current member data is missing for preparing or saving the partial TP.

What to do: Wait for current member state and check their partial TPs.

About 5 seconds
Error / block#D99A92
A shared SL or partial SL price is invalid for a member.

Why: The common price falls outside the SL range of at least one position.

What to do: Select an SL price valid for every member and check the level bounds.

About 5 seconds
Error / block#D99A92
Shared trailing gap placement began without a shared start.

Why: A shared gap was selected but its corresponding start has not been set.

What to do: Set the shared trailing start first, then return to the gap.

About 5 seconds
Error / block#D99A92
The BE / trailing start is not beyond every entry on the profit side.

Why: The start must be on the profit side of each entry, not just the group average.

What to do: Check the start against every entry rather than only the group average.

About 5 seconds
Error / block#D99A92
A shared BE / trailing price is outside a member range.

Why: The selected price violates at least one member individual bounds.

What to do: Check each position BE or trailing range and select a valid common price.

About 5 seconds
Error / block#D99A92
A position, partial or its settings changed during placement.

Why: The position identity, selected partial or its configuration changed during the gesture.

What to do: Cancel stale placement with Esc and select the required partial level again.

About 5 seconds
Error / block#D99A92
A partial trailing price is invalid for a member.

Why: Validation would clamp the price into the member range, so the original price is rejected.

What to do: Check entry, target, start and gap of partial trailing for each affected member.

About 5 seconds
Please note

LOW MARGIN: two different colors

A reduced preview volume is a warning. The post-send reduction message uses the error channel.

Current code behavior

PTT SAVED uses an error border

If saving PTT returns additional explanation, this message uses the error channel. The word SAVED does not select the color.

5 secondsErrors, queued in order
3 secondsClose Now information
While the action is activePlacement and submission phases

Ordinary hints and Close Now depend on SHOW_CANVAS_HINTS. Errors and submission safety states stay enabled. When both appear, the error takes the first row below the menu and the hint takes the next row.

Reference to current code: AppNotifications · AppPlacementHint · AppError · ThemePresets
〈Brackets〉 mark variable text. Checks and broker responses may supply different reasons.
Checked against code: Magic Entry 3.43 · 17 November 2026

Notification preview