EA errors
Find your PineConnector or MetaTrader error code, understand what stopped the request, and check the cause.
Find the code and full message in your logs, then use the matching entry below. Before resending an alert, check the receiving account for existing orders and positions.
If the alert never reached PineConnector, use Troubleshoot an alert.
Find your error
Section titled “Find your error”| Source | Code |
|---|---|
| PineConnector EA | 7001 · 7002 · 7003 · 7004 · 7005 · 7006 · 7007 · 604 |
| MT5 | 4752: trading disabled · 4756: request failed |
| MT4 | MT4 error reference |
| MT4 or MT5 | Zero divide |
Find the logs: on Edge, select the affected instance in Portal → Edge → Experts / Journal. On a self-hosted terminal, open Experts and Journal. Match the account, symbol and event time.
PineConnector EA codes
Section titled “PineConnector EA codes”7001–7007 mean the EA stopped before submitting the affected order to the broker. These codes were introduced in EA 3.54.5. Follow the relevant check, then test the correction on demo and verify the resulting order.
7001: Missing sizing value or stop loss
Section titled “7001: Missing sizing value or stop loss”Loss-based sizing needs a loss budget and a stop loss in the same alert. Supply both:
- One volume method:
vol_pct_bal_loss=for a percentage of balance,vol_pct_eq_loss=for a percentage of equity, orvol_dollar=for an amount in account currency. - One stop method:
sl_pips=,sl_price=orsl_pct=, with a valid non-zero stop distance.
For an older alert, check Volume Type and Target Type before converting risk= or sl=. Replace each legacy field with the explicit method that preserves its intended units; keep one method per value. See older-alert guidance.
If you intended a fixed lot size, use vol_lots= instead. This changes the sizing method: the stop no longer determines the lot size. See complete alert examples.
7002: Tick value unavailable
Section titled “7002: Tick value unavailable”The broker did not supply the symbol’s tick value, which the EA needs for sizing.
Confirm the exact symbol is available and receiving quotes during its trading session. On self-hosting, show it in Market Watch. If the value remains unavailable, contact your broker; on Edge, include the hosted logs when contacting Support.
7003: Invalid broker symbol data
Section titled “7003: Invalid broker symbol data”The symbol’s tick size, point size or volume step is zero, so the EA cannot calculate a valid lot size.
Check the symbol specification with your broker. On self-hosting, you can restart MT5 when it is safe to interrupt signal processing, then recheck the data. On Edge, contact Support with the symbol and logs. Changing the alert’s volume does not repair missing broker data.
7004: Stop-loss distance is zero
Section titled “7004: Stop-loss distance is zero”The stop resolves to zero distance, so loss-based sizing cannot calculate lots.
Check the stop’s units and value: use sl_pips= for a distance, sl_price= for a price, or sl_pct= for a percentage of entry price. For an entry, the stop must be on the correct side and away from the applicable entry price. An older sl= value follows Target Type.
7005: Margin could not be calculated
Section titled “7005: Margin could not be calculated”MT5’s margin calculation failed or returned zero for margin-based sizing (vol_pct_bal_margin=). This does not by itself mean the account has insufficient funds.
Check that the symbol is tradeable and quoting. Send Support the full log, including the accompanying MT5 error number. Margin allocation is not a loss limit; do not switch sizing methods just to bypass this error.
7006: 100-lot safety stop reached
Section titled “7006: 100-lot safety stop reached”The calculated size triggered the EA’s 100-lot safety stop.
Review the selected volume method, its value and, for loss-based sizing, the stop distance. Reduce the sizing value to request a smaller position. A very small stop distance can produce a large calculated size. The broker’s own volume limits still apply.
7007: Unsupported order type for margin sizing
Section titled “7007: Unsupported order type for margin sizing”The margin-sizing calculation received an unsupported order type. This is not expected in normal use.
Contact Support with the alert, EA version and full log. Do not guess a replacement command or repeatedly resend the alert.
604: Pending entry is on the wrong side
Section titled “604: Pending entry is on the wrong side”The pending-entry price is on the wrong side of the market for the command:
| Above market | Below market |
|---|---|
buystop or selllimit |
buylimit or sellstop |
Compare against your broker’s current quote. Use entry_price= for an exact price, entry_pips= for a pip distance, or entry_pct= for a percentage distance. Relative entry distances must be positive; the command determines the side. Choose one method and check the broker’s minimum distance. Change the command only if that matches your intended order type. See pending-order syntax.
MetaTrader 5
Section titled “MetaTrader 5”EA trading is disabled
ERR_TRADE_DISABLED: automated trading is not permitted.
Check permissions on the terminal that received the alert.
- Edge
Inspect the affected instance’s Experts / Journal logs, EA Settings and Connections → account → Terminal info. Contact Support with the error and event time. Changing Algo Trading in a local terminal does not change Edge.
- Self-hosted MT5
Enable Algo Trading in the toolbar and allow algorithmic trading in the PineConnector EA’s properties. Both permissions are required.
Trade request could not be sent
ERR_TRADE_SEND_FAILED is a general request failure. The accompanying message identifies the next check.
Match the accompanying Experts / Journal message to a case below.
Match the message beside 4756
Section titled “Match the message beside 4756”| Message | Check first | Next action |
|---|---|---|
| Unsupported filling mode | The symbol’s permitted order-filling policy | Check the broker’s supported filling policy. On older self-hosted EAs, use Broker Set B only if your version supports it and it matches the broker. Edge: send the log to Support; change Broker Set only on their advice. |
| No prices | Symbol selection, connection and incoming quotes | Confirm the exact symbol is quoting during its session. On self-hosting, show it in Market Watch. Edge: check the same broker account’s symbol/session and send hosted logs to Support if quotes remain unavailable. Do not keep resending. |
| Invalid request | Exact symbol and the full request parameters | Check the exact broker symbol, supported order type and every parameter in the alert against Syntax. |
| Trade disabled | Whether the account and symbol permit this trade | Check the symbol’s session and account restrictions with your broker. For EA permissions, follow 4752. |
| Invalid expiration | The pending order’s expiration policy | Check the broker’s pending-order expiration rules. On older self-hosted EAs, confirm support before using Broker Set C. Edge: send the request and logs to Support before changing Broker Set. |
| Invalid volume | Minimum, maximum and volume step | Compare requested lots with the broker’s minimum, maximum and step. For entries, use vol_lots= for fixed lots or the appropriate explicit volume method. For closelongvol/closeshortvol, risk= is still required as lots to close. |
| Invalid stops | Target units, correct side and minimum distance | Follow the stops checklist. |
| Requote | The current quote and execution mode | Check the current quote and broker response. Confirm whether any order was placed before retrying. Investigate repeated requotes with your broker on demo. |
| Invalid price | Price validity for that symbol and order | Check the price increment, direction and distance of the pending entry, stop loss and take profit. |
Compare the accompanying message with MetaTrader trade-server return details. PineConnector also uses 4756 for a volume-close alert missing risk=. An Invalid Volume label alone does not prove a broker rejection; 4756 alone does not select one fix.
Check stops and prices
Section titled “Check stops and prices”Use this checklist for MT5 Invalid stops/Invalid price or MT4 130:
- Use explicit units for current MT5 alerts. Choose
sl_pips=,sl_price=orsl_pct=for the stop; usetp_pips=,tp_price=ortp_pct=for the target. Do not put an absolute price into a pip field. Oldersl=/tp=values follow Target Type; for older EAs, check version-compatible syntax. Exception: conditional manual breakeven still usessl=0; do not replace it withsl_pips=0. - Check the correct side. For an open buy position, SL must be below your broker’s current Bid and TP above it; for an open sell, SL must be above the current Ask and TP below it. When modifying a stop, the original entry price alone is not the side check. For a pending order, SL and TP must fit the pending entry price and direction.
- Check minimum distances. Read Stops level in the broker’s symbol specification, or ask your broker/Support for it. It is shown in points, not pips. One PineConnector pip is 10 quoting points.
- Check price increments. The broker must accept the requested price step and decimal precision.
- Check pending entries separately. The entry price and expiration can be invalid even when SL and TP are acceptable.
See MetaTrader’s MT5 stop and freeze-level rules and MT4 trade limits for the broker-level constraints.
MetaTrader 4 errorsOpen this reference only if your terminal is MT4.
These checks apply to MetaTrader 4. Choose the matching error below; the shared stops checklist and Zero divide guidance remain available outside this section.
Invalid stops
ERR_INVALID_STOPS: a stop or pending-entry level is invalid for the request.
Check the target units and pending-entry setting supported by your MT4 EA version.
- Inspect the symbol specification
Check minimum stop distance, price increments and the current broker quote.
- Review the actual levels
Use the stops-and-prices checklist above. Correct the parameter or level, then repeat a controlled demo test.
Invalid trade volume
ERR_INVALID_TRADE_VOLUME: the requested lot size does not meet the broker’s rules.
Open the symbol specification and compare minimum volume, maximum volume and volume step with the requested lots.
- Check how the EA calculated the size
Confirm your Volume Type and the value supplied in the message. Decimal places alone do not establish a valid volume step.
Market closed
ERR_MARKET_CLOSED: the symbol is outside its trading session.
Check that symbol’s trading hours on your broker’s server, including holidays and session breaks.
- Wait for a valid session
Send a new test only when the symbol is open and quotes are available.
Trading disabled
ERR_TRADE_DISABLED: trading is not available for this account or symbol.
Confirm the exact symbol and whether your broker permits trading it on this account.
- Check the local setup
Show the symbol in the Symbols list and confirm the EA’s live-trading permission is enabled.
- Separate a broker restriction from an EA issue
On a demo account, check whether an equivalent manual trade is permitted. Ask the broker about a restriction if manual trading is blocked too.
Not enough margin
ERR_NOT_ENOUGH_MONEY: the account does not have enough available margin for the request.
Read the required and available margin in the Experts output.
- Review the requested size
Confirm Volume Type before reducing a risk/volume value. Existing positions and broker margin rules affect what is available.
- Escalate an apparent mismatch
If the log shows sufficient available margin but the broker rejects the trade, send the full request and broker response to support.
DLL calls are not allowed
ERR_DLL_CALL_NOT_ALLOWED: the required DLL permission is disabled.
Review Allow DLL imports in both MetaTrader Options and the PineConnector EA’s properties.
- Check your environment
Your self-hosted computer or VPS must support the PineConnector EA’s required DLL usage. Follow the MT4 setup guide for its current files and permissions.
Invalid function parameter
ERR_INVALID_FUNCTION_PARAMETER_VALUE: a function received an invalid value.
Read the full error and compare your message with the required fields for that command.
- Check entry sizing fields
Check the required volume field in your MT4 EA’s version-compatible syntax. This code alone does not identify which parameter is wrong.
- Keep the failing example
If the message matches the reference, send the exact request and log to support instead of adding guessed parameters.
Unknown symbol
ERR_UNKNOWN_SYMBOL: MetaTrader does not recognise the requested symbol.
Copy the name exactly from your broker’s Symbols list, including capitalisation and any suffix.
- Check any mapping
Confirm that TradingView placeholders or Symbol Mapping resolve to that exact name. EURUSD and eurusd are not interchangeable in the documented syntax.
Trading is not allowed
ERR_TRADE_NOT_ALLOWED: automated trading permission is disabled.
Enable automated trading in Tools → Options → Expert Advisors, then check Allow live trading in the EA’s Common tab.
- Confirm the EA is ready
Check the AutoTrading toolbar state and the EA’s chart status. Use a demo request to verify the permission change.
Chart object does not exist
ERR_OBJECT_DOES_NOT_EXIST: a chart object expected by the program was not found.
Save the full error and the surrounding Experts output.
- Send the context to support
Include the EA version, event time, Signal ID where available, and what you were doing when the error appeared. Do not assume changing trade size will fix a chart-object error.
For another MT4 code, use the official MQL4 error list. Confirm the terminal platform before applying its checks.
Zero divide
Section titled “Zero divide”A calculation attempted division by zero
The program could not complete a calculation. The location and surrounding log are needed to investigate the cause.
Record the complete message, including any line/column numbers shown in brackets, and your PineConnector EA version.
- Preserve the request and environment
Keep the Signal ID, symbol, relevant EA settings and Experts/Journal lines around the event.
- Report the issue
Send that evidence to PineConnector Support. Do not repeatedly resend a live request while its outcome is uncertain.
Still stuck, or using Edge?
Section titled “Still stuck, or using Edge?”Send PineConnector Support:
- The full error, surrounding Experts / Journal lines, event time and time zone.
- The Signal ID, exact broker symbol, alert message and expected result.
- Your EA version and whether you use Edge or self-hosting.
Share account details privately only when needed. Remove passwords and secret= values from messages and screenshots. Saved self-hosted logs can help if the on-screen entries are incomplete.
For an MT5 code not listed here, use the official MQL5 runtime error list.


