MT4 request troubleshooting note

Prepared from the user’s observations. No live server check, automatic diagnosis or permission to resend is implied.
MT4 codes only. A moving quote or a completed checklist does not prove that execution is available. This tool never connects to a broker, sends an order or transmits your note.

Illustrative case — invented symbols, times and log lines; not an actual broker incident.

Your recorded facts

Message or code:
136 · Off Quotes

Requested action:
Close a position

Result of this request:
Explicitly rejected

Platform used:
MT4 desktop

Request origin:
Manual

Connection observed:
Connected

Prices for this symbol:
Updating

Symbols affected:
One symbol

Trading session checked:
Confirmed open

Earlier message:
Different rejection found

Exact symbol, including suffix:
EURUSD.demo

Incident time as displayed:
2026-10-20 14:32:08

Time zone or UTC offset:
UTC+02:00 — fictitious displayed offset

Broker / server label:
DEMO-BROKER / DEMO-SERVER (invented)

Exact message:
Off quotes (136)

Relevant earlier log lines:
14:32:06 Request rejected: trading disabled (133)
14:32:08 Off quotes (136)
Invented excerpt; no real order identifier.

Request details / failed function:
Manual request to close an existing position. The rejection is recorded; the position remains visible as open.

Other useful observations:
Prices were updating. This observation does not establish that the requested close could be executed.

Your next check
Based only on your selections. These are checking steps, not a finding about the cause.
Read the earlier rejection in context
Keep the previous message alongside Off Quotes, with timestamps and the affected operation. Some brokers document earlier rejections as useful clues. The earlier message is not automatically the cause of every later error; ask the broker to interpret the sequence if needed.

Checks to keep with the note

1. Check the position and protection that remain
A rejected close or modification does not remove the existing position or apply the requested protection. Verify the actual remaining state; use the broker’s verified contact channel if normal order handling is unavailable.

2. Save the exact request message
Record the action, exact symbol and relevant error text. A current chart price is not the request’s execution confirmation.

3. Confirm the exact tradable symbol
Check suffix, specification, current availability and whether the instrument has been replaced or restricted by this broker.

4. Read surrounding log entries
On MT4 desktop, inspect Journal and, for automation, Experts. Read relevant earlier rejections. Some broker-specific instructions point elsewhere, such as a mailbox; that route is not universal.

5. Share a minimal, redacted note
Check the downloaded TXT before sending it through the broker’s verified support channel. Keep passwords, access keys, account numbers and unrelated history out of the note.

Review and redact this file before sharing. No automatic sending or saving to a broker account takes place.