Repository navigation
Troubleshooting
Status: active Category: E (product / user) Created: 2026-10-31 Last updated: 2026-10-31 Owner: TCS team
Every entry below is a failure that has actually happened on this project, with the misleading message it produced. That matters: the most expensive ones do not look like errors.
schema.prisma is not the complete schema. Several tables are managed in raw SQL — the trade
execution queue among them. db push treats an unmodelled table as garbage and drops it with the
data still inside. It does not error; it warns and waits for a y.
npm --prefix nest run db:check # read-only; names any table the schema does not know aboutCreate tables from the SQL in nest/prisma/, then npx prisma generate for types only.
The API is running and holds the file. This is not a broken install, and reinstalling does not help.
npm --prefix nest run build:api # stop → build → restart → health checkMeans there is no build — the entry point is nest/dist/src/main.js, one directory deeper than
nest start looks. Run npm --prefix nest run build:api. node_modules, or run prisma db push — is wrong twice over.
MySQL is not running. Start it, then confirm the connection string in nest/.env. Note the password is
supposed to be yours; if you copied an example, it will not work.
Normal. It means Redis and the job queue are unavailable, which is the expected state for a local install. The database is still connected and scoring still runs. Do not restart the API to "fix" it.
Check, in order:
-
Is any data provider healthy?
curl http://localhost:3201/api/health— theprovidersblock reportstotal,healthy,degraded,failed. Several adapters need an API key; a few need none. - Are there symbols? An empty watchlist scores nothing, and an empty app is the designed default.
-
Is a bot subscribed to a protocol? A bot without a
strategy_protocolsubscription is never queued, silently.npm --prefix nest run audit:bot-activationnames the reason per bot.
GET :5000/health tells you which of several things it is, and gives a remedy:
| Field | Reads | Means |
|---|---|---|
connectionState |
terminal-down |
MetaTrader 5 is not running, or was not logged in |
credentialMismatch |
non-null | this bridge is attached to an account it was not configured for — reads work, orders are refused |
tradeAllowed |
false |
the terminal's Algo Trading button is off — every order will be refused with retcode 10027
|
tradeapiDisabled |
true |
the terminal's API trading path is disabled — a second, independent blocker |
tradeAllowed: null means unknown, not off: it is null when the bridge could not ask.
# Windows
netstat -ano | findstr :3201
taskkill /PID <pid> /FRun cd nest and npm install there. The --prefix form fails if nest/package.json cannot be
resolved from where you are.
The API serves a build, not the TypeScript sources. Rebuild with npm --prefix nest run build:api.
Frontend changes are picked up by Vite's dev server automatically.
Ask in Discussions with the command you ran and the output you got. A defect with a reproduction is an issue; a question is a discussion.
Trading Command Suite · Financial Disclaimer · Installing · FAQ
Source · AGPL-3.0 · Issues · Discussions Built by Ryan Bayne · FifeCIC
💚 Support this project → — free, complete, no premium edition, and no income.
🛑 Not financial advice. The app ships unconfigured and is not set up to make money for you. Test on a demo account before connecting anything real.
v0.162.0 · alpha · © 2026 Ryan Bayne / FifeCIC · AGPL-3.0 · generated from the repository — corrections belong in the repo, not this page.
🛑 Financial Disclaimer — read before connecting an account.
🌐 Website · Screenshots
💚 Support this project — the app is free, complete, and has no income.
Start here
Understand
- How it works
- Glossary
- Scoring architecture
- Risk controls
- How a bot becomes a trade
- Screener contract
- Trading constraints
- Readiness tiers
- Notice codes
Help