Alert History
The Alert History page provides an in-depth look at all the trading alerts you’ve sent to CrossTrade, giving you key insights into their execution process.
Within the Alert History page, you can:
✅ Track All Sent Alerts – View a list of all trading alerts you've sent through CrossTrade.
✅ Check Execution Status – Instantly see whether an alert was successfully processed or if it encountered an issue.
✅ Analyze Execution Time – See exactly when CrossTrade received the alert and how long it took to forward it to NinjaTrader (NT).
✅ Multi-Account Order Tracking – If your order request was part of a multi-account placement order (e.g., account=Sim101,Sim101,etc;), you can automatically retrieve all associated alerts by clicking on the Multi-Account ID.
Understanding Your Alerts
Each alert in the Alert History contains detailed information about the trade request, including:
Alert Timestamp – The exact time the alert was received by CrossTrade.
Execution Time – How long it took for the alert to be processed and sent to NinjaTrader.
Order Details – The full command that was sent, including order type, quantity, and price levels.
Multi-Account ID – If your order was placed across multiple accounts, clicking this ID will display all related alerts in one view.
Status Indicators – Alerts are marked as Success, Pending, or Failed, allowing you to quickly identify which orders were executed correctly and which need further review.
Error Messages – If an alert failed, you’ll receive detailed information explaining why, such as invalid formatting, unsupported commands, or connection issues.
Troubleshooting Failed Alerts
We recently introduced a new help modal system that provides attitional info and possible solutions for each Error or Warning you may encounter. Below you will find a complete table with additional info to help troubleshoot when and why these errors occur.
Position Out of Sync
What does this mean?
This error occurs when the position quantity in your NinjaTrader account does not match what CrossTrade expects based on the signals received.
Common Causes
Manual trades (exits) executed directly in NinjaTrader
Orders filled at different prices or partially filled
Connection interruption during order execution
Multiple signal sources sending conflicting orders
How to Fix
Review XT Add-On logs for specific info about what is out of sync
Verify your NinjaTrader account shows the expected position
If sync fails, flatten the position and restart from a clean state
Consider adding strategy_exit_block to block strategy exits if manual intervention is intended
XT Add-On Disconnected
What does this mean?
CrossTrade cannot communicate with your NT8 installation. The XT Add-On is not connected or not running.
Common Causes
NinjaTrader 8 is not running
XT Add-On is not connected or installed in NinjaTrader
Firewall blocking the connection
NinjaTrader crashed or was forcefully closed
How to Fix
Open the XT Add-On in NinjaTrader and click Connect
Restart NinjaTrader if the add-on appears stuck
Reinstall the XT Add-On if not visible in NinjaTrader "New" dropdown
Signal Formatting Error
What does this mean?
The webhook signal received by CrossTrade does not match the expected format. This prevents the signal from being processed.
Common Causes
Missing required fields in the webhook payload
Incorrect syntax like JSON in TradingView alert message
Missing semi-colons at the end of lines
Including any extra text or characters outside the expected format
How to Fix
Review the error message for specific formatting issues
Check your TradingView alert message against the documentation
Use the Command Builder tool to generate correct syntax
Reference examples on the Dashboard and in the documentation
Rate Limit Exceeded
What does this mean?
Excess signals have been sent in a short period of time over what was set in your Rate_limit.
Common Causes
Strategy sending excessive signals (possible Pine Script bug)
Multiple alerts triggering simultaneously
Webhook loop or misconfiguration
Rate limit ID shared across multiple strategies
How to Fix
Review your strategy logic for potential issues
Use unique rate limit IDs for different strategies
Increase the rate limit window if legitimate high-frequency signals
Ignore if occasional spikes are expected
Outside Trade Window
What does this mean?
This signal was blocked because it arrived outside your configured trading hours or on a non-trading day.
Common Causes
Signal sent during configured off-hours set on your Master Controls
Signal sent during trade window restrictions in NT Account Manager
Wrong timezone setting in alert or account settings
Holiday or weekend when markets are closed
How to Fix
Review your Master Control settings in Account Management
Review your NT Account Manager for trade window settings
Review your alert-level trading window settings
Use "bypass_trade_windows" flag in alert message if override needed
Kill Switch Engaged
What does this mean?
All trading has been disabled via the master kill switch. This is a safety feature to immediately stop all automated trading.
Common Causes
Global Kill switch enabled in Master Control Panel
NT Account Manager kill switch activated
Alert-level kill switch flag used
How to Fix
Locate source of kill switch activation and disable
Review recent trading activity before re-enabling
Ensure the reason for kill switch activation has been addressed
Closing Only Mode
What does this mean?
Account is set to closing only mode. New positions cannot be opened, but existing positions can be closed.
Common Causes
Closing only mode enabled in Master Control Panel
Account set to closing only in NT Account Manager
How to Fix
Check XT Control Panel closing only setting
Review monitor in NT Account Manager for closing only status
Maximum Quantity Exceeded
What does this mean?
The signal was blocked because it would exceed the maximum position count for this account.
Common Causes
Your account has reached its maximum allowed based on your max_position setting
How to Fix
Review max position settings in your alert
Adjust value if needed to allow more total positions at one time
Missing Required Field
What does this mean?
A required field in your webhook signal is empty or missing. CrossTrade cannot process the signal without all required fields.
Common Causes
Missing KEY field in your alert message
Missing ACCOUNT field in your alert message
Missing INSTRUMENT field in your alert message
Field exists but has no value (e.g., ACCOUNT=;)
How to Fix
Check the error message to see which specific field is missing
Add the required field to your TradingView alert message
Ensure the field has a value (not empty)
Use the Command Builder to generate proper syntax with all required fields
Request Timed Out
What does this mean?
The signal was sent but CrossTrade did not receive a response from NinjaTrader within the expected timeframe.
Common Causes
XT Add-On disconnected after signal was sent
NinjaTrader froze or became unresponsive
Network connectivity issues between CrossTrade and NT8
NinjaTrader is processing too many signals at once
How to Fix
Check if XT Add-On is still connected in NinjaTrader
Restart NinjaTrader if it appears frozen or unresponsive
Check your internet connection stability
Reduce signal frequency if sending too many signals simultaneously
Market Data Unavailable
What does this mean?
NinjaTrader cannot access market data for the specified instrument. This is required for order execution.
Common Causes
Instrument not added to NinjaTrader database
Data feed provider disconnected or not subscribed
Incorrect instrument symbol format
Market is closed and historical data not loaded
How to Fix
Verify the instrument exists in NinjaTrader Tools > Instruments
Check your data feed connection status in NinjaTrader
Ensure you have an active subscription for this instrument with your data provider
Try loading a chart for the instrument to initialize market data
Account Inactive
What does this mean?
Your CrossTrade account does not have an active subscription. Signals cannot be processed without an active plan.
Common Causes
Subscription has expired
Payment failed or was declined
Trial period has ended
How to Fix
Visit crosstrade.io/pricing to view available plans
Check your payment method is up to date
Contact support if you believe this is an error
Invalid Secret Key
What does this mean?
The secret key in your webhook signal is missing, incorrect, or has been deactivated. Every request must include a valid secret key to authenticate.
Common Causes
KEY field is missing from alert message
Typo in the secret key value
Key was regenerated but alert not updated
How to Fix
Copy your secret key from the CrossTrade dashboard
Paste the key into your TradingView alert message
Ensure no extra spaces or characters around the key
Regenerate the key if needed and update all alerts
Unknown Command Type
What does this mean?
The command type in your signal is not recognized by CrossTrade.
Common Causes
Typo in the COMMAND field (e.g., PLAC instead of PLACE)
Using a command that does not exist
Missing COMMAND field entirely
Extra characters or spaces in command name
How to Fix
Check the documentation for valid command types
Common commands: PLACE, CLOSEPOSITION, FLATTEN
Use the Command Builder to generate correct syntax
Ensure COMMAND field has no typos
No Positions to Exit
What does this mean?
You attempted to exit or flatten a position, but no matching position exists in the specified account or instrument.
Common Causes
Position was already closed by a previous signal
Position was manually closed in NinjaTrader
Wrong instrument symbol in the alert
Wrong account specified in the alert
How to Fix
Verify the position exists in NinjaTrader before sending exit signals
Check that instrument symbol matches exactly (including contract month)
Ensure account name in alert matches NinjaTrader account
This may be expected behavior if position was already closed
TradingView Placeholder Not Replaced
What does this mean?
Your alert contains TradingView placeholder syntax (like {{strategy.order.action}}) that was not replaced with actual values. These variables can only be sent from a TradingView Strategy alert. Sending them from the dashboard Manual Trader or from an Indicator will encounter this error.
Common Causes
Placeholder syntax used outside of a strategy alert
Strategy does not provide the requested placeholder value
Typo in placeholder name
Using placeholders in a manual/indicator alert
How to Fix
Placeholders only work with strategy alerts, not indicator alerts
Verify placeholder names match TradingView documentation exactly
Test your strategy to ensure it generates the expected values
Use static values instead if placeholders are not supported
Account Not Connected
What does this mean?
The specific NinjaTrader account referenced in your signal is not currently connected, even though the XT Add-On may be running.
Common Causes
Data connection for this account is not active
Prop account has been disqualified and disabled
How to Fix
Open NinjaTrader and verify the account appears in the Accounts tab
Check your data connection status
Account Not Found
What does this mean?
The account name specified in your signal does not exist in NinjaTrader. This is not a CrossTrade specific issue, we are processing the trade request and receiving a rejection.
Common Causes
Typo in the account name
Account name is case-sensitive
Account was removed or renamed
Using wrong account name format
How to Fix
Check the exact account name in NinjaTrader Accounts tab
Account names are case-sensitive - ensure exact match
Update your alert with the correct account name
Common format: Sim101, APEX-XXXX, etc.
Market Position Requirement Not Met
What does this mean?
Your signal requires a specific market position (long, short, or flat) that does not currently exist. This is often international to filter signals and can be ignored
Common Causes
Trying to add to a position that does not exist
Trying to add a position when already in the opposite position
Trying to add a position when not in a flat state
How to Fix
Verify your current position in NinjaTrader matches expectations
Check if a previous signal already closed the position
Instrument Format Not Compatible
What does this mean?
The instrument format in your alert is not compatible with NinjaTrader 8.
Common Causes
An error in the formatting or syntax of the instrument symbol
A pine script bug that provides an incorrect ticker variable
A non-existant instrument symbol on NT8 (e.g., alt crypto symbols)
How to Fix
Use TradingView continuous contracts (MES1!, NQ1!, ES1!) - CrossTrade auto-converts these
Or use NT8-compatible formats: MES 12-25, MES DEC25, or MESZ5
Change your TradingView chart to continuous contract before creating alerts
Update your alert's INSTRUMENT field with a compatible format
Unknown Field Name
What does this mean?
Your alert contains a field name that CrossTrade does not recognize. Only documented field names are supported.
Common Causes
Creating custom field names like TP_TICKS, TP_PRICE, SL_TICKS that do not exist
Typo in a valid field name (e.g., ACCT instead of ACCOUNT)
Using field names from other platforms that are not supported
Copying syntax from non-CrossTrade documentation (e.g., JSON)
How to Fix
Check the error message to see which specific field is not recognized
Review the CrossTrade documentation for valid field names
Use the Command Builder to see all available fields
Remove or rename the custom field to match CrossTrade's supported fields
Why Alert History Matters
The Alert History page is essential for traders who want full visibility into the trading signals sent to CrossTrade. Whether you’re troubleshooting a failed alert or tracking multi-account orders, this page is a crucial part of using CrossTrade.
Last updated