First identify the account provider, stage, actual platform and issued Rithmic System. Then separate provisioning, authentication, data entitlement and trading restrictions. A generic reconnect or reset cannot resolve every provider-side problem.
Educational software guidance. Trading involves risk. Read the financial and information disclaimers.
Locate the failure
| Symptom | Evidence and next step |
|---|---|
| No credentials issued | Check account provisioning with the firm; do not invent a login |
| Credentials rejected | Match trading credentials and assigned System, excluding copied spaces |
| Account missing | Check exact login/account assignment, activation and platform entitlement |
| Quotes missing | Check contract session, exchange agreements and data/depth access |
| Order rejected | Preserve the exact response and compare the account risk rules |
| Liquidation/admin-only | Ask the provider about the current mode and authorized clearing process |
| Works in one app only | Compare connector permission, direct/plugin route and platform licence |
Use provider-specific facts
Apex's documented System is Apex; Bulenox and Leeloo publish Paper Trading routes. Earn2Trade changed its provided NinjaTrader access in June 2026. TopstepX credentials are not a Rithmic login. Follow the dated firm setup references, not a generic evaluation/funded server table.
Preserve order state before recovery
Inspect positions, working orders and local strategy/copier dependencies before ending a session or retrying a signal. Rithmic's current FAQ says post-liquidation restrictions can require manual clearing; a new calendar day is not proof of recovery.
Send a useful support record
Use the firm's official support channel with the account ID privately, program stage, platform/build, issued System, timestamp/timezone and full error. Include redacted relevant logs and describe what still works. Keep passwords and API tokens out of screenshots and public posts. The platform vendor handles its connection/software behavior; the issuing provider controls account assignment and risk permission.
Screenshot references


Common questions
Should I change to Rithmic 01 after passing?
Only if that is the new issued assignment.
Does a blank quote prove an expired account?
No. Session, instrument and data entitlement can explain it.
Will liquidation-only clear tomorrow?
Do not assume that. Follow the current provider/Rithmic mode rules.
Should I open a second session to test?
Check concurrent-session permission and existing local dependencies first.