“{symbol} is already subscribed on this login” (rp_code 1029)
Rithmic answers rp_code 1029, “update bit type already exists”, when a subscription to the same instrument already exists on your login. The connection is fine; the stream is held elsewhere, most often by a second copy of Senzoukria or another platform on the same login.
Senzoukria · Troubleshooting · Updated September 2026
At a glance
- Message
- “{symbol} is already subscribed on this login”
- Rithmic code
- rp_code 1029, “update bit type already exists”
- Certainty
- The only refusal the app states as established: the server says the subscription exists
- Button
- “Retry once the other session is closed”
What you see
A refusal notice titled “{symbol} is already subscribed on this login”, with the line “What is established: the server itself states that the subscription already exists. What it does not say is which program is holding it.” It may sit on an empty chart while the connection badge reads CONNECTED; the notice explains that in that case the connection is fine and the stream is held elsewhere.
Why it happens
A login gets one subscription per instrument. The server keeps the existing one and refuses the duplicate. Three holders produce exactly the same answer: a second Senzoukria window or process, another platform signed in with the same broker login, or a subscription the server has not yet released after a hard shutdown of the app that held it.
If data is already on screen, the refusal only concerns a duplicate request and nothing was lost.
How to fix it
- Close the other Senzoukria windows, including any copy left running in the notification area.
- Click “Retry once the other session is closed”, or reload the chart.
- If the refusal comes back, close any other platform signed in with the same broker login.
- After a crash, wait a few minutes: a subscription the server kept open clears by itself a few minutes after the app that held it is gone.
What it is not
- Not a data entitlement problem: the server confirms a subscription exists.
- Not a broken connection: the login went through.
- Not always another Senzoukria window: closing Senzoukria windows does not help when another platform or a stale server-side subscription holds it.
When to contact support
If the problem persists, contact support through Menu → Report a problem, or on the Senzoukria Discord. Use “Copy the exact message” and mention which platforms were open on the same login. Your broker can tell you how many simultaneous sessions your login may open.
Related pages
- Broker refused the subscription
- Broker refusals and connection errors
- Market data entitlement
- Data feed
In the same section
- Diagnostic: session already running
- Bridge drift badge
- History load already running
- Subscription required or expired
- GEX key required
- Alpaca unauthorized
- Anthropic refused this key
- NinjaTrader bridge stuck connecting
This page in other languages
Frequently asked questions
- Why is this the only refusal the app calls certain?
- Because the broker states it literally: the subscription already exists. Every other refusal is shown with possible causes only.
- Can two platforms share one Rithmic login?
- That depends on your broker’s session limits. Ask how many simultaneous sessions your login may open; the app gives you the exact question to send.