The Market Robo™
The Market Robo™
Support

Problems & Solutions

Saw a code like TMKR-3001 in MetaTrader? Search it below for the exact cause and a step-by-step fix.
53 known codes
Show fixes for:

Setup & configuration

TMKR-1001
Error
Vendor

Invalid product configuration (robot version ID)

The robot or indicator was built with a version ID that is not a valid 36-character UUID, so the SDK refused to start.
TMKR-1002
Error
Customer

API key is required

No API key was entered, so the product cannot authenticate with TheMarketRobo.
TMKR-1003
Error
Vendor

Robot configuration class missing

A robot (EA) was started without a valid IRobotConfig instance, which the SDK requires for remote configuration.
TMKR-1004
Warning
Vendor

Indicator short name not set (cannot be remotely removed)

The indicator did not register a short name before init, so the platform cannot remove it from the chart if a session is terminated server-side.
TMKR-1005
Error
Customer

This product session was terminated

A previous session on this chart was terminated by the platform, leaving a block file that prevents the product from restarting here.
TMKR-1006
Warning
Customer

Saved session could not be restored (started fresh)

An indicator could not reuse its saved session after a chart or timeframe change and safely started a brand-new session instead. This is informational and self-healing.

Authentication & licensing

TMKR-2001
Error
Vendor or customer

Invalid API key

The API key was not recognised by the platform, so the session was refused.
TMKR-2002
Warning
Vendor or customer

Authentication required

A request reached the platform without a valid authorization token. This is usually transient SDK plumbing during start-up or reconnect.
TMKR-2003
Error
Customer

Session token expired

The short-lived session token expired and could not be refreshed in time, usually after a network interruption.
TMKR-2004
Error
Vendor or customer

Authentication token invalid

The session token was rejected or could not be read. The session was invalidated for safety.
TMKR-2005
Error
Vendor or customer

License expired or not yet started

The license tied to this API key is outside its valid date range, so the platform refused the session.
TMKR-2006
Error
Vendor or customer

License inactive

The license exists but is marked inactive, so it cannot start a session.
TMKR-2007
Error
Vendor or customer

License not found

The platform could not find a license record for this session. This usually points to a data issue and needs support.
TMKR-2008
Error
Vendor

Robot version does not match the license

The version ID compiled into the product does not match the version the license (or submission) authorises.
TMKR-2009
Error
Vendor

Submission is not in a testable state

A test license tried to start a session while its submission is in a status that does not allow testing.
TMKR-2010
Error
Vendor or customer

Session does not belong to this caller

A request tried to act on a session that is not associated with the presented credentials.

Connectivity & terminal settings

TMKR-3001
Error
Vendor or customer

Network requests are not allowed (WebRequest not enabled)

MetaTrader blocked the robot's request to themarketrobo.com because the URL is not in the allowed WebRequest list.
TMKR-3002
Error
Customer

Invalid server address

MetaTrader reported the TheMarketRobo address as invalid (MQL error 5200).
TMKR-3003
Error
Customer

Cannot connect to the server

MetaTrader could not establish a connection to themarketrobo.com (MQL error 5201).
TMKR-3004
Warning
Customer

Connection timed out

The request to themarketrobo.com took too long and timed out (MQL error 5202).
TMKR-3005
Error
Customer

Connection refused

The connection to themarketrobo.com was actively refused (MQL error 5203).
TMKR-3010
Error
Customer

DLL imports are disabled (indicators)

An indicator needs DLL imports to reach themarketrobo.com, but DLL imports are turned off so it cannot connect.
TMKR-3011
Error
Customer

Indicator network request failed (WinINet)

An indicator's HTTP request through the system network library failed for a reason other than DLL imports being off.
TMKR-3020
Error
Customer

Could not connect to TheMarketRobo service

A request to the platform did not reach it at all (no HTTP response). The product could not start or maintain its session.
TMKR-3040
Warning
Customer

Terminal not connected / account data unavailable

The product started but MetaTrader had no live account data yet, so telemetry values may report as zero.
TMKR-3050
Warning
Customer

Too many requests (rate limited)

The platform temporarily throttled requests because too many arrived in a short window.

Session & heartbeat

TMKR-4001
Warning
Vendor or customer

Heartbeat sequence mismatch (auto-resynced)

A heartbeat arrived with an out-of-order counter; the SDK resynchronises automatically. This is informational and self-healing.
TMKR-4002
Error
Customer

Connection lost — product removed after repeated heartbeat failures

The product could not reach the platform for several consecutive heartbeats and removed itself from the chart to avoid running unmonitored.
TMKR-4003
Error
Customer

Session not found or no longer active

A request referenced a session that has already ended or does not exist.
TMKR-4004
Error
Vendor or customer

Maximum concurrent sessions reached

The license already has as many active sessions as it allows, so a new one was refused.
TMKR-4005
Warning
Customer

Session already ended

An action was sent for a session that has already been closed.
TMKR-4006
Warning
Vendor

A change request is already pending

A new config or symbol change was requested while a previous one for the same session is still being applied.
TMKR-4007
Warning
Customer

Session end request failed

The product could not deliver its final "end session" message, usually because the connection was already gone. The product is still removed.
TMKR-4008
Error
Vendor

Request failed validation

The platform rejected a request because its contents were invalid (for example a robot session without a magic number).
TMKR-4009
Error
Vendor

Invalid request format

A request was sent in a format the platform could not parse (for example a missing or wrong Content-Type).
TMKR-4010
Error
Vendor

Missing required field

A request was missing a field the platform requires (for example the heartbeat sequence number).

Configuration & symbols

TMKR-5001
Warning
Vendor

Config field rejected — invalid value

A remote configuration change was refused because the value failed the robot's own validation rules.
TMKR-5002
Warning
Vendor

Config field rejected — out of range

A remote configuration change was refused because the numeric value was outside the field's allowed minimum/maximum.
TMKR-5003
Warning
Vendor

Config field not found

A remote configuration change referenced a field that the robot's config schema does not define.
TMKR-5004
Warning
Vendor

Config field is read-only

A remote configuration change tried to modify a field marked read-only.
TMKR-5005
Info
Vendor

Config change feature is disabled

A configuration change arrived but the robot has the remote-config feature switched off, so it was ignored.
TMKR-5010
Warning
Vendor

Symbol not found in session

A symbol change targeted a symbol that was not part of the robot's initial session symbol list.
TMKR-5011
Warning
Vendor or customer

Symbol unavailable (rejected by terminal/broker)

MetaTrader refused to enable a symbol the robot tried to activate.
TMKR-5012
Warning
Customer

Trading disabled for symbol

Trading is not currently allowed for the targeted symbol.
TMKR-5013
Info
Vendor

Symbol change feature is disabled

A symbol change arrived but the robot has the symbol-change feature switched off, so it was ignored.

Termination & lifecycle

TMKR-6001
Error
Vendor or customer

Session terminated by the platform

The platform asked the product to stop and remove itself, for a reason supplied in the message.
TMKR-6002
Error
Customer

Authentication failed during refresh — product removed

The product could not renew its session token and removed itself to avoid running unauthenticated.
TMKR-6003
Error
Customer

Indicator could not be removed automatically

The platform asked an indicator to remove itself but MetaTrader did not complete the removal, so it must be removed by hand.
TMKR-6004
Error
Customer

Indicator disabled by safety fallback

After a terminated session could not be cleanly removed, the indicator stopped drawing and blocked itself from restarting until you remove it.

Platform & system

TMKR-9001
Error
Vendor or customer

Internal server error

The platform hit an unexpected error while handling the request. These are usually transient and retried automatically.
TMKR-9002
Error
Vendor or customer

Database error

The platform could not complete a database operation for the request.
TMKR-9003
Error
Vendor or customer

Cache error

The platform could not reach its session cache for the request.
TMKR-9010
Error
Customer

Product could not start (internal initialization failure)

The SDK could not set itself up inside MetaTrader, usually due to low memory or a transient terminal state.
Still stuck?If the code isn't listed or the fix didn't help, open a support ticket with the code and your license ID and we'll get you sorted.