Troubleshooting
Common issues and solutions for Nyria automation.
This guide covers common issues you might encounter and how to resolve them.
First, check the basics: Before diving into troubleshooting, verify:
- Bot is Active (not paused)
- Strategy is Active (validated)
- Integration is Connected (not reauth required)
- Alert format matches what you validated
Alert Source Issues
TradingView Alerts Not Firing
Possible Causes:
- Repainting strategy - Your strategy shows signals historically but doesn't fire them in real-time
- Webhook delay - TradingView webhooks can be delayed 2-45+ seconds (they consider this normal)
- Alert not triggered - Condition hasn't been met
- Webhook URL incorrect - Typo or wrong URL
Solutions:
- Verify your strategy doesn't repaint (learn more)
- Wait up to 60 seconds for delayed webhooks
- Check TradingView alert history to confirm it fired
- Verify webhook URL matches exactly
Discord/Telegram Alerts Not Processing
Possible Causes:
- Bot not in channel - Nyria bot doesn't have access
- Author filter mismatch - Alert sent by different user
- Keyword filter mismatch - Alert doesn't contain required keyword
- Message edited - Edited messages may not be re-processed
Solutions:
- Verify Nyria bot is in the correct channel
- Check author filter settings
- Remove keyword filter to test
- Send a new message (don't edit)
Strategy Issues
"Could not parse alert"
Cause: Alert format doesn't match expected structure.
Solutions:
- Ensure alert includes instrument, direction, and action
- Check spelling of instrument names
- For options, verify strike and expiration format
- Review validated alert examples
"Instrument not allowed"
Cause: Alert instrument not in strategy's allowed list.
Solutions:
- Add instrument to strategy's allowed instruments
- Check spelling matches exactly (SPY not Spy)
- For crypto, ensure pairing matches (BTCUSDT not BTCUSD if only USDT selected)
"Multiple entries disabled"
Cause: Strategy doesn't allow multiple simultaneous positions.
Solutions:
- Wait for current position to close
- Enable "Allow Multiple Entries" in strategy settings
- Check if position is actually open
"No option contracts found"
Cause: Option strike or expiration not available.
Solutions:
- Adjust DTE range to include available expirations
- Check delta/price targets are reasonable
- Verify instrument has options (not all stocks do)
- Ensure market is open for option data
"Strategy not active"
Cause: Strategy requires revalidation after changes.
Solutions:
- Go to Integration tab
- Revalidate alert formats
- Ensure all alert types have valid examples
- Check for validation errors
Bot Issues
"Bot not executing"
Causes and Solutions:
Bot is paused:
- Check bot status is Active
- Click Start Bot if paused
Integration disconnected:
- Check integration status
- Reconnect if showing "Reauth Required"
Insufficient buying power:
- Check broker account balance
- Reduce position size
- Close other positions to free capital
Instrument not selected:
- Verify alert instrument is in bot's selected instruments
- Add instrument to bot configuration
Strategy not active:
- Check strategy status
- Revalidate if required
"Order rejected by broker"
Common Causes:
Insufficient funds:
- Check available buying power
- Reduce position size
- For spreads, ensure margin for max loss
Invalid option:
- Strike not available
- Expiration date passed
- Contract doesn't exist
Account restrictions:
- Pattern Day Trader limits
- Options trading not enabled
- Margin account required for shorts
- Crypto not supported on account
Market hours:
- Some order types restricted outside regular hours
- Use limit orders for extended hours
"Partial fill on spread"
Cause: Some legs filled, others didn't.
What Happens:
- Remaining legs tracked separately
- Will exit on next exit signal
- Partial position maintained
Solutions:
- Use market orders for better fill rates
- Widen limit prices for spreads
- Trade more liquid options
- Check broker logs for details
Integration Issues
"Reauth required"
Cause: OAuth token expired.
Solution:
- Click the integration
- Click Reconnect
- Complete OAuth flow
- Integration status updates
"Integration disconnected"
Causes:
- Token revoked at broker
- Account closed
- API access disabled
Solutions:
- Check broker account status
- Verify API permissions
- Reconnect integration
- Contact broker support if needed
"OAuth failed"
Solutions:
- Clear browser cookies and cache
- Try incognito/private browsing
- Disable popup blockers
- Check broker site isn't down
- Try different browser
Position Issues
"No position found to exit"
Cause: Exit alert but no open position exists.
What Happens:
- Logged as WARNING (not error)
- Any pending entry orders are cancelled
- No trade executed
Common Reasons:
- Position already closed
- Entry never filled
- Wrong instrument in exit alert
- Position closed manually at broker
"Exit quantity exceeds position"
Cause: Trying to close more than you have.
Solutions:
- Check actual position size at broker
- Verify position wasn't partially closed
- Ensure bot position size matches reality
"Cannot close spread - missing legs"
Cause: Some spread legs already closed or never opened.
What Happens:
- System exits remaining legs only
- Tracks partial close
- Logs which legs were missing
Solutions:
- Check broker for manual closures
- Verify all legs filled on entry
- Review entry execution logs
Validation Issues
"Price required for limit order"
Cause: Strategy configured for alert-specified price but alert has none.
Solutions:
- Include price in your alerts
- Change limit order target to bid/ask/mid
- Use market orders instead
"Ambiguous crypto symbol"
Cause: Strategy has both USDT and USDC pairs selected, alert doesn't specify which.
Example:
- Strategy allows: BTCUSDT and BTCUSDC
- Alert says: "BTC" (ambiguous)
Solutions:
- Specify exact pair in alert: "BTCUSDT"
- Or select only one pairing in strategy
"Strike price invalid"
Cause: Option strike is unreasonable or not available.
Solutions:
- Check strike is in reasonable range
- Verify strike exists in option chain
- Adjust delta/price targets
- Check DTE range includes available dates
Performance Issues
"Slow execution"
Causes:
- High market volatility
- Broker API delays
- Network latency
Solutions:
- Use market orders for speed
- Check broker status page
- Verify internet connection stable
"Orders not filling"
Causes:
- Limit price too aggressive
- Low liquidity
- Market moved away from limit
Solutions:
- Widen limit prices
- Use market orders
- Trade more liquid instruments
- Check broker's order book
Logging Issues
"No logs appearing"
Causes:
- No alerts received yet
- Strategy not active
- Bot paused
Solutions:
- Send test alert
- Check strategy status
- Verify bot is active
- Check webhook URL is correct
"Logs show errors but no details"
Solutions:
- Expand metadata in log entry
- Check broker logs for broker-specific errors
- Review strategy configuration
- Contact support with log ID
Getting Help
Check Logs First
- Strategy Logs - Shows parsing and validation
- Bot Logs - Shows execution and broker responses
- Metadata - Expand for detailed error info
Information to Provide
When contacting support, include:
- Strategy ID
- Bot ID (if applicable)
- Timestamp of issue
- Log entries (with metadata)
- Alert that failed (if applicable)
- Broker and account type
Contact Support
- Discord - Join our community server
- Email - support@nyria.io
- In-App - Use the help widget
Prevention
Best Practices
- Test First - Use paper trading for at least 1-2 weeks
- Verify Alerts - If using TradingView, confirm your strategy doesn't repaint
- Start Small - Small position sizes initially
- Monitor Daily - Check logs and positions every day
- Maintain Capital - Keep 2x required buying power for entries AND exits
- Understand Risks - Know maximum loss scenarios for your strategy
- Validate Thoroughly - Test all alert types before going live
- Use Dedicated Account - Don't mix manual trading with automation
Common Mistakes
- Insufficient capital for exits (especially credit spread exits)
- Not testing with paper accounts long enough
- Ignoring reauth notifications until trades fail
- Setting position size too large
- Not understanding spread mechanics
- Forgetting about margin requirements
- Using TradingView strategies that repaint
- Expecting immediate execution (TradingView delays can be 25-45s)
- Not monitoring positions ("set and forget" mentality)
Remember: Automated trading is NOT "set and forget." Things can and will go wrong. You are responsible for monitoring your positions and intervening when needed. Read our Known Limitations to understand what can fail.
Next Steps
- Known Limitations - Understand platform limitations
- Risk Disclosure - Full risk documentation
- Strategy Logs - Review parsing and validation
- Bot Management - Manage your bots
- Glossary - Key terms and definitions
- Contact Support - Submit a ticket