Appearance
Are you an LLM? You can read better optimized documentation at /troubleshooting/instance-pause-reactivation.md for this page in Markdown format
Instance Pause & Reactivation
Your TTMT trading service runs as its own always-on instance behind the scenes. Occasionally that whole instance can be paused — not one broker connection, but the entire service — and you'll land on a paused or reactivation screen instead of your dashboard. This page explains what that state is, why it doesn't put your data at risk, and how to get trading again. The single most important thing to know up front: an infrastructure pause is not a billing problem.
Limited preview
Reason-aware instance pause and self-service reactivation are in limited preview and are rolling out gradually. What you see may differ slightly from what's described here, and the exact reactivation path may change. If you're stuck, contact support and they'll reactivate you directly.
What a paused instance is
TTMT can pause your trading instance for operational reasons that have nothing to do with your subscription. The two common ones:
- A long gap in use — if an account goes unused for an extended period, its instance may be paused to free up resources. Coming back and reactivating brings it right back.
- Onboarding that never finished — if you signed up but never completed the steps that stand your service up (connecting a broker, connecting Telegram), the instance can be paused until you pick the setup back up.
In both cases the pause is reason-aware: TTMT knows why it paused, and the screen you see reflects that reason rather than a generic error.
Your data and configuration are safe
A pause does not delete anything.
- Your settings, config profiles, channel assignments, and symbol mappings are preserved exactly as you left them.
- Your trade history and signal logs stay intact.
- Reactivating restores your service to where it was — you are not rebuilding from scratch or re-entering anything.
The pause takes your live processing offline (no new signals are handled while paused), but it never discards the configuration behind it.
How to reactivate
Limited preview
The self-service reactivation button is part of the limited preview. If you don't see it, that's expected — contact support and they'll reactivate the instance for you.
- Open your dashboard. If your instance is paused, you'll see the paused/reactivation screen instead of the normal view.
- Follow the reactivation prompt shown there. If your pause was due to incomplete onboarding, this may route you back to the setup step you left off at.
- Give the service a moment to come back up — your broker and Telegram connections re-establish, and your existing configuration loads.
- Confirm your account connections show healthy before you expect signals to trade again.
An infrastructure pause is not a billing suspension
This is the distinction that trips people up, so it's worth being blunt about it.
| Infrastructure instance pause | Billing suspension | |
|---|---|---|
| What it is | The platform paused your trading instance for an operational reason (unused gap, unfinished onboarding). | Your subscription lapsed — failed payment, expired plan, or a cancellation that reached the end of its cycle. |
| Is your subscription affected? | No. Your plan can be perfectly current and paid. | Yes — this is the subscription problem. |
| What it costs to fix | Nothing. Reactivating does not charge you or change your plan. | Resolve the payment or resubscribe. |
| Where to go | Reactivate here, or contact support. | Billing issues and Suspended account. |
If your subscription is current, a "paused" screen is not a payment problem
Don't update your card or resubscribe to fix an infrastructure pause — that won't do anything, because nothing is wrong with your billing. Reactivate the instance (or ask support to), and leave your subscription alone.
If you genuinely do have a lapsed subscription, that's the other path — see Billing issues and Suspended account, which cover the read-only state and how to restore access.