Skip to main content

Troubleshooting

Most Signal Share situations are visible from one of two places: the source card on /user/signal-share (live state, active and pending counts, per-source log) or your NinjaTrader activity log (the per-signal messages).

CrossTrade tells me my add-on is too old​

Signal Share requires CrossTrade NT8 add-on v1.13.0 or later. CrossTrade shows a notice in your NT8 if it sees an older version.

Fix. Update the add-on from crosstrade.io/download and restart NT8. Settings push through automatically once the new add-on is up; nothing else needs to happen.

An invite fails with "User not found" or "You can't invite yourself"​

Each of your NinjaTrader installations signs in with its own CrossTrade login, and invites go from the broadcasting login to the email address on each receiving login.

  • User not found. No CrossTrade login uses that email address. Check the address on the login you use for the receiving installation.
  • You can't invite yourself. You entered the email of the broadcasting login. A login cannot receive its own broadcast, so the receiving installation needs its own CrossTrade login.

My broadcast source shows zero connections but I sent invites​

The source card shows two numbers:

  • Connections. Receiving logins that accepted your invite and have an active connection.
  • Pending. Invited logins that have not accepted yet (accepting includes the Risk Release Agreement).

If a number is stuck on Pending, that login has not accepted yet. Sign in with it and accept from Pending Invites on /user/signal-share, or resend the invite if needed.

I changed a setting but nothing happened​

Settings push from CrossTrade to your add-on continuously. In normal operation a change is live within a few seconds. If your add-on is offline, the change is queued and applied the next time the add-on reconnects.

If you are sure the add-on is online and a change is not taking effect:

  • Toggle the source's Active switch off and on, which forces a refresh.
  • Check that your add-on is on v1.13.0 or later. Older add-ons do not receive Signal Share settings.

My receiver missed a signal​

Signal Share is best-effort. A receiving installation can miss a signal if its NinjaTrader was offline at the moment the broadcast went out, or if the broadcasting installation's connection was momentarily disrupted. CrossTrade holds your last 100 broadcasts for 5 minutes, and a receiving add-on on v1.13.8 or later that reconnects in that time receives what it missed automatically. Anything older is gone.

If position alignment matters to you, turn on Sync Strategy and Target Quantity on the broadcast source (on your broadcasting login). With those on, the next signal carries the broadcasting account's intended position size and pulls the receiving account back into alignment automatically. See Broadcaster configuration.

Receiver's activity log shows a Signal Share error​

Errors at this level usually mean the local order could not be placed. Common causes:

  • The mapped account no longer exists or is logged out. Check the account selector on the connection card.
  • The instrument is not available on your broker connection.
  • A strategy lock blocked the order, or your strategy-tag mode is set to skip and the broadcasting account's tagged position cannot land.

The activity-log entry names the account and the instrument so you can see which leg of the setup is involved.

Broadcast log shows "rate-limited"​

CrossTrade caps how many signals one broadcasting login can send in 10 seconds. Past 100 it drops order modifications, and past 300 it drops everything. This is a safety net against runaway loops: if a strategy bug or a stuck external system causes a flood of orders on the broadcasting account, the cap prevents that flood from reaching every receiving account.

Fix. Stop the source of the surge. The count resets after 10 seconds.

A connection I removed still shows in the source's count​

Counts update on a short rolling cadence. If a removal does not show up after a couple of minutes, the connection may have been re-created by an open invite link being clicked again. Check the source's pending count.

Where to find the details​

For deeper inspection:

  • Broadcasting side. /user/signal-share → Broadcasting tab → source card → See Logs. Per-source broadcast log with the signal, command, instrument, and per-receiver delivery status.
  • Receiving side. /user/signal-share → Receiving Signals tab → connection card → See Logs. The receiving log.
  • Activity log inside NinjaTrader. The authoritative source for per-signal events on the receiving side.

If you reach support, include the signal identifier shown in either log and the timestamps from both sides. That is enough to trace a signal end to end.