Troubleshooting FAQ
Most Common Issues
Section titled “Most Common Issues”🔴 Error Messages
Section titled “🔴 Error Messages””Script took too long to execute” error
This is TradingView’s most common performance-related error. It means your current TradingView plan doesn’t provide enough resources for the indicator’s complex calculations. Our Professional Edition indicators perform deep, multi-layered analysis which can be computationally intensive.
Quick fixes (try in order):
- Reduce Lookback Period: In the indicator settings, lower the main lookback period (e.g., from
500
to200
bars). - Disable Visuals: Turn off any visual plots or tables you don’t actively need. For example, disable the decaying function visualisation in Flux Composer.
- Use a Higher Timeframe: Switch from a lower timeframe to a higher one (e.g., from 15m to 1h). Calculations are performed per-bar, so higher timeframes require less computation.
- Isolate the Indicator: Temporarily remove other indicators from your chart to confirm which one is causing the issue.
Best Solution: Upgrade TradingView Plan If the error persists, the most reliable solution is to upgrade your TradingView plan. Higher-tier plans provide significantly more server-side resources and longer calculation times.
”Study Error” or “Cannot read properties”
This error usually indicates a temporary issue with the indicator’s state on your chart or a version mismatch after an update.
Solution:
- Remove the problematic indicator from your chart.
- Hard Refresh your browser or TradingView app (Ctrl+F5 on Windows, Cmd+Shift+R on Mac).
- Re-add the indicator to your chart.
- Start with Default Parameters: Always use the default settings first to ensure the indicator loads correctly before making adjustments.
”Invalid parameters” error
This means an input value in the indicator’s settings is outside the allowed range or in the wrong format.
Fix:
- Use the “Reset Settings” button in the indicator configuration window to return to default parameters.
- Hover over the parameter name to see tooltips with valid ranges.
- Ensure numeric fields do not contain any text characters.
- Do not exceed the minimum or maximum values specified for a parameter.
🟡 Connection Problems
Section titled “🟡 Connection Problems”Signal Provider missing from Flux Composer dropdown
This is our #1 support question. The cause is almost always the loading order of the indicators on your chart. Flux Composer can only see Signal Providers that were already loaded before it was.
The Fix (follow this order precisely):
- Remove BOTH the Signal Provider and Flux Composer from your chart.
- Add the Signal Provider FIRST.
- Wait a few seconds for it to fully load and initialize. You should see its plots appear on the chart.
- THEN, add the Flux Composer. The Signal Provider should now appear in the dropdown menu in the Flux Composer’s settings.
Still not working?
- Hard refresh your browser or app (Ctrl+F5 or Cmd+Shift+R).
- Check versions: Ensure both indicators are from the same edition (e.g., both Pro or both CE). You cannot mix them.
- Try on a clean chart layout to rule out conflicts with other indicators.
Indicators not communicating (no signals in Flux)
If Flux Composer is loaded but not showing any signals from the provider, check this list:
- Same Chart: Are both indicators on the exact same chart panel?
- Same Timeframe: Are they both operating on the same timeframe?
- Loading Order: Did you follow the precise loading order described above?
- Fully Loaded: Wait for both indicators to complete their initial calculations.
- Compatible Versions: You cannot connect a CE Signal Provider to a Pro Flux Composer, or vice-versa.
🟢 Performance Issues
Section titled “🟢 Performance Issues”Chart is slow, lagging, or freezing
Complex indicators can strain your browser or TradingView app, especially on lower-tier plans.
Immediate fixes:
- Reduce Bars on Chart: In Chart Settings → Symbol, reduce the “Bars on chart” to a smaller number like 1000 or 500.
- Disable Unused Visuals: In the settings for each GYTS indicator, turn off any plots, tables, or colour-fills you don’t need for your analysis.
- Isolate Components: Use one complex indicator (like Flux Composer or Order Orchestrator) per chart layout. Use a second chart for other tools.
- Close Other Tabs: Free up browser memory by closing other intensive tabs and applications.
Best solution: The TradingView Desktop App generally offers better performance than the browser version. Upgrading your TradingView plan also provides more resources.
Browser running out of memory
Solutions:
- Use the TradingView Desktop App. It’s optimized for performance.
- Close unused chart tabs within the app/browser.
- Restart your browser or the TradingView app every few hours to clear its memory cache.
- Disable resource-heavy browser extensions that might interfere with TradingView.
🔵 Configuration Problems
Section titled “🔵 Configuration Problems”Too many signals (overtrading)
Quick fixes in Flux Composer:
- Increase Signal Threshold: Raise the Upper/Lower Thresholds. For example, from
0.5
to0.7
. This requires a stronger consensus from the signal providers. - Switch to a Higher Timeframe: A 1h chart will naturally have fewer signals than a 5m chart.
- Add a Filter: Use a second Signal Provider in “Filter” mode within Flux Composer (Pro feature) to add another layer of confirmation.
Target: Aim for 2-5 high-quality signals per day on your primary trading timeframe, not a constant stream of noise.
Too few signals (missing opportunities)
Quick fixes in Flux Composer:
- Decrease Signal Threshold: Lower the Upper/Lower Thresholds. For example, from
0.5
to0.3
. - Switch to a Lower Timeframe: A 15m chart will offer more opportunities than a 4h chart.
- Check your Filters: Ensure your filter settings in Flux Composer or Order Orchestrator aren’t too restrictive.
Note: Quality over quantity is a core principle. It’s better to miss a mediocre signal than to take a bad one.
Market Regime seems wrong
The Market Regime Detector’s perception can be tuned to your timeframe and market.
- Regime changes too often?
- Decrease
Sensitivity
: Makes the detector less reactive to minor changes. - Increase
Adaptability
: Provides more stable, longer-term regime detection.
- Decrease
- Regime is too slow to change?
- Increase
Sensitivity
: Makes the detector more responsive to regime changes. - Decrease
Adaptability
: Allows faster adaptation to new market conditions.
- Increase
Alerts not triggering
Common mistakes when setting up TradingView alerts:
- Condition is too specific: Instead of
Crossing Value 0.7
, useGreater Than Value 0.69
. This prevents missing alerts due to rounding. - Wrong Frequency: Set the alert to trigger
Once Per Bar Close
for confirmed signals, notOnly Once
. - Alert Expires: Ensure your alert’s expiration time is set far enough in the future.
- Conflicting Conditions: When creating an alert with multiple conditions, ensure they can logically happen at the same time. Test with a simple condition first.
🟣 Visual & Versioning Issues
Section titled “🟣 Visual & Versioning Issues”My indicator settings look different from the documentation
This is almost always due to a version difference.
- Community Edition (CE) vs. Professional (Pro): The Pro editions have far more features, settings, and customisation options. The CE versions are simplified for learning. Make sure the documentation you’re reading matches the indicator edition you’re using.
- Outdated Version: While invite-only scripts update automatically, sometimes you might be using an older version cached by TradingView. See the topic below.
How do I get the latest version of an indicator?
Pro (Invite-only) Scripts:
TradingView automatically updates invite-only scripts. When we publish an update, you get it instantly. If you suspect you have an old version:
- Remove the indicator from your chart.
- Hard refresh your browser/app (Ctrl+F5 or Cmd+Shift+R).
- Re-add the indicator. This will ensure you have the absolute latest version.
CE (Public) Scripts: Public scripts do not update automatically. To get the latest version, you must remove the old one from your chart and re-add it from our TradingView profile.
⚫ Access & Subscription Issues
Section titled “⚫ Access & Subscription Issues”Pro indicators not showing after subscribing
This is a synchronisation issue between Whop and TradingView. Follow these steps carefully.
- Verify Subscription: Check your Whop dashboard to ensure your subscription is active.
- Check Connected Accounts: Go to your Whop Settings and confirm your TradingView username is linked exactly as it appears on TradingView.
- Check Invite-Only Scripts: In TradingView, go to Indicators → Invite-only scripts. This is where they will appear.
- Wait 10-15 minutes: It can take some time for access to propagate.
- Hard Refresh / Restart: A hard refresh (Ctrl+F5) or restarting the TradingView app is often the final step needed.
Discord role not assigned
To get your @goemon-warrior
role for YaeBot access and priority channels, you must link your Discord account in Whop.
- Ensure Subscription is Active on Whop.
- Join our Discord Server: Use the official invite link: discord.gg/M4HaeP69Mj.
- Connect Discord in Whop: Go to your Whop Settings and connect the correct Discord account.
- Wait 5 minutes: The Whop bot will automatically assign your role.
If it fails, try leaving and re-joining the Discord server to re-trigger the bot.
Lost access after a successful payment
If your payment went through but you lost access, it’s typically a temporary sync issue.
Immediate Checks:
- Check Payment Status: Did the payment fully process in your bank/card statement?
- Check Whop Dashboard: Does it show an active subscription?
- Check Correct Accounts: Are you logged into the correct TradingView and Discord accounts that are linked in Whop?
If the issue persists for more than an hour, please contact support with your Whop transaction ID and username.
Universal Fixes
Section titled “Universal Fixes”When in doubt, these four steps solve over 80% of all issues.
- Hard Refresh: Press Ctrl+F5 (Windows) or Cmd+Shift+R (Mac) to clear the cache and reload.
- Remove & Re-add: Remove all GYTS indicators and add them back in the correct order (Signal Provider first).
- Use Default Settings: Reset the indicator to its default parameters to establish a working baseline.
- Test on a Clean Chart: Use a new, blank chart layout to rule out conflicts from other scripts or drawings.
Still Stuck?
Section titled “Still Stuck?”Where to get help:
- For strategy and setup questions, ask our Discord community.
- For account, billing, or persistent technical issues, contact support.