Step-by-step fixes for signal delivery, trade execution, broker connections and sizing problems.
Four checks resolve most reports. Do them in order before reading further — the answer is usually here.
If it is on, the signal is sitting in the approval queue waiting for you.
A daily drawdown limit pauses execution silently by design. The signal log names the limit that blocked it.
The instrument must exist at your broker under that exact name. Unknown symbol is the most common rejection.
Zero, below the broker minimum, or above your max lot cap all result in a rejection.
The source must be linked to the account you are watching. An unlinked account never receives anything.
Open the channel's administrator list. Channel owners remove bots more often than you would think.
Open the channel under Channels — the Active toggle must be on.
A require-list that no message matches is the classic cause of a channel going quiet. Clear it and re-test.
Run /verify again with a fresh token from Channels → Add Telegram Source.
If messages appear there but produce no signal, it is a parsing problem, not a connection problem — see signal formats.
Alerts → History. If it shows a delivery error, the request never reached PipSync and the problem is the URL.
Settings → Advanced → TradingView Alerts. Regenerating the token invalidates the old URL immediately — paste the current one.
One missing comma or a smart quote pasted from a document breaks the whole payload.
Webhooks require a paid TradingView subscription. Free accounts cannot send them at all.
Settings → Advanced → TradingView Alerts → Recent alerts lists every call that reached PipSync, with the parser error if it was rejected. Empty means TradingView never arrived.
Under Channels — server access is not channel access, each channel is selected explicitly.
Channel overrides beat server roles. The PipSync role needs View Channel and Read Message History on that channel.
Re-running OAuth refreshes an expired token and any permissions added since.
Screenshots cannot be parsed. Look at the raw log to see what actually arrived.
Character for character, from your terminal. This is the cause more often than everything else combined.
A live login on a demo server fails with the same error as a wrong password.
If MetaTrader itself cannot connect, the account is disabled or the password needs resetting at the broker.
Two platforms trading one login produce trade-context errors and inconsistent state. Give PipSync its own account.
Nightly broker maintenance disconnects everything. It reconnects on its own; verify nothing was missed.
An explicit size in the message bypasses percentage sizing, capped by your max lot.
A micro or suffixed variant has a different contract size, so the same lot number means a different exposure.
Each account sizes from its own equity — 0.5% of a 100k challenge is not 0.5% of your 5k live account.
A very tight stop produces a large position for the same risk budget. That is the formula working, not a bug.
The full calculation is in Position sizing.
If you have been through the relevant section and it still misbehaves, open a ticket with the raw signal text, the timestamp with your timezone, the account name and what you expected. That combination is usually enough to answer without a second round trip.
Send the raw signal, the timestamp and the account name — that is usually enough to answer on the first reply.