STANCEL MANUAL 1.020

If something goes wrong

Ordered by what you see, not by what it is.

Nothing shows up

What you see What it usually is
Stancel isn't in the NavigatorIt was copied into the installation folder instead of the data one. Menu File → Open Data Folder
It's in the Navigator but dragging it draws nothingMetaTrader needs restarting
The panel appears but not the mosaic or the drawingStancel_Lienzo.ex5 is missing from MQL5\Indicators\

The canvas one is the most common failure and the worst to diagnose, because it throws no error at all: the desk asks for it by name, doesn't find it, and there simply is no drawing. It looks like Stancel is broken.

It won't let you trade

What you see What it usually is
The SEND button does nothingIt isn't armed. Flip the switch up
Armed, and it's still doing nothingConfirmation is missing — or it expired (90 s, or you moved the plan)
"ACCOUNT NOT AUTHORISED: only trades on DEMO"It's a real account. SETTINGS → Funding → Allow trading on a REAL account
"DAILY LIMIT reached"The guard has braked. It rearms tomorrow
Nothing on the panel can tradeMetaTrader's Algo Trading button is red
"NOT SENT: the plan couldn't be saved"The settings store is full

That last one deserves an explanation: with no saved plan there's nothing to check what went out against, afterwards. It would rather not send than send something that can't later be audited.

The guard isn't watching

What you see What it usually is
The spheres show dashes instead of figuresThe challenge's starting balance is missing
"UNKNOWN: no account data"The terminal hasn't connected yet. Wait a few seconds
The figures don't match your funding firm'sCheck how it measures: on balance or on equity. Both switches are in Funding
The safety stop tripped and you don't know whyThe panel states the reason in those words. The two that close are: daily limit and total limit. Your own cap never closes, it only warns

⚠️ With the starting balance at zero, the safety stop can't trip. It's not a bug: there's simply nothing to measure against. The panel says so at the foot of the guard.

The panel looks wrong

What you see What to do
It doesn't fit the screenSETTINGS → Chart → Panel density
The text looks tiny or hugeIt's Windows scaling; the panel adapts when MetaTrader restarts
It flashes too muchTurn off "Flash when a figure changes"
A chart won't let you drag itRun the STC_LiberarGrafico script
A module moved and won't come backThe layout is saved; move it again and it stays

Telegram

It has its own section: Telegram alerts.

The essentials: if nothing arrives, check that the service is running (Navigator → Services), that the token is pasted in, and that you've written to the bot from your Telegram.

Things that look like bugs and aren't

The plan doesn't draw itself. It's born when you press NEW PLAN. This was a decision: it used to appear on its own and there was no way to remove it.

The desk always starts disarmed, and in CAUTION mode. There's no setting to change that. Of the two mistakes possible at startup, only trading too big costs money.

Reaching the target doesn't stop you. It tells you and that's it. Your funding firm doesn't force you to stop either, and this guard exists to prevent disasters, not to supervise you.

The safety stop also closes what you opened by hand. This is deliberate: the drawdown belongs to the account, not to Stancel's orders.

Renko and range bars leave the indicators without data. That's the factory state: the “Renko brick” setting (SETTINGS → Indicators) comes at 0, and at 0 the series isn't built. Set a value and they're served; the panel warns instead of quietly falling back to time candles.

Before writing something off as broken

Two checks that solve half the cases:

1. Look at the version in the panel's title. It has to match the one in the MANIFIESTO.txt of the package you installed. If it doesn't match, that terminal has a different Stancel. 2. Look at whether the Algo Trading button is green. Red, and no MetaTrader expert can trade.

If it still isn't working

Note down three things before writing in: