Pine Script Alert Debugger

I have analyzed your Pine Script alert logic and identified issues with the payload structure and trigger frequency.

[Pine Script Alert Debug Report]

🚨 Alert Trigger Issues:

• Missing barstate.isconfirmed check. This alert will fire on every tick where the condition is met, even if the bar hasn't closed, leading to "repainting" alerts.
• High frequency risk: The current logic does not restrict the alert to once per bar.

📡 Webhook Payload Validation:

• Invalid JSON: The keys and string values are missing double quotes (").
• Syntax Error: Using string concatenation inside the message parameter is less reliable than using TradingView's placeholder syntax for webhooks.

🔔 Duplicate Fire Prevention:

• Missing freq or once parameter in alertcondition(). In the UI, this defaults to "Only Once," but programmatic logic should ideally handle state to prevent spamming.

️ The Fix:

// Add barstate check to your condition logic
longConfirmed = longCondition and barstate.isconfirmed

// Corrected alertcondition with valid JSON payload and placeholders
alertcondition(longConfirmed, 
     title="Buy", 
     message='{"action": "buy", "price": "{{close}}", "ticker": "{{ticker}}"}')

[Self-Check]

• Alert trigger conditions validated for barstate and timing
• Webhook payload syntax checked for valid JSON
• Duplicate fire prevention verified
• Corrected code provided with proper parameters

Next steps

1. Update your script with the barstate.isconfirmed logic to ensure the candle is closed.
2. Copy the new JSON payload into your TradingView alert settings box.
3. Perform a test fire on a lower timeframe to confirm 3Commas accepts the new format.