Skip to main content

Telegram Troubleshooting

Solutions to common Telegram bot issues.

Bot Not Responding​

Symptoms​

  • Bot doesn't respond to commands
  • Messages are sent but no reply

Solutions​

  1. Check bot is admin

    • Group Settings → Administrators
    • Bot must be listed as admin

  2. Verify bot is in group

    • Search for the bot in group members
    • Re-add if not found

  3. Test with /help

    /help

    If this works, bot is responding

  4. Check webhook (self-hosted)

    • Verify webhook URL is set correctly
    • Check Cloudflare Worker logs

/setup Failed​

"Brand not found"​

  • Verify Brand ID is correct
  • Must be 42 characters
  • Must start with 0x
  • Find in Partner Portal → Settings → Account

"Not an admin"​

  • Add bot as group administrator
  • Verify you have admin rights
  • Try again after adding

"Already configured"​

Group is already connected. Use /config to view settings.

Rewards Not Processing​

Symptoms​

  • Users run /daily but don't get RSNC
  • GM/GN not being rewarded

Solutions​

  1. Check cooldown

    • User may have already claimed today
    • 24-hour cooldown is standard

  2. Verify event is enabled

    • Partner Portal → Events
    • Check telegram_daily_checkin is enabled

  3. Check brand balance

    • Partner Portal shows brand RSNC balance
    • Fund if empty

  4. Verify event exists

    • Check Partner Portal → Events
    • Create if missing

GM/GN Not Detecting​

Symptoms​

  • Users say "gm" but don't get rewarded

Solutions​

  1. Check event is enabled

    • Partner Portal → Events
    • gm_checkin should be enabled

  2. Verify cooldown

    • User may have already claimed today

  3. Check message format

    • "gm" must be at the start of message
    • Supported: gm, good morning, morning!

  4. Verify bot can see messages

    • Bot needs to be admin to see all messages

Streaks Resetting Unexpectedly​

Symptoms​

  • User's streak reset to 1
  • "I checked in yesterday!"

Solutions​

  1. Grace period expired

    • Check when last check-in was
    • Default grace: 24 hours

  2. Timezone differences

    • Resets at midnight UTC
    • Users in different timezones may be confused

  3. Missed a day

    • Grace period starts from last check-in time
    • Not from midnight

Balance Not Showing​

Symptoms​

  • /balance shows 0 or error

Solutions​

  1. Wallet not created yet

    • First reward creates wallet
    • User needs to claim something first

  2. API connectivity issue

    • Try again in a few minutes
    • Check status.rsnc.network

Perks Not Loading​

Symptoms​

  • /perks shows empty or error

Solutions​

  1. No perks created

    • Create perks in Partner Portal
    • Perks → Create Perk

  2. Perks not enabled

    • Check perk status in Partner Portal

  3. API issue

    • Try again later

Claim Failed​

Symptoms​

  • /claim returns error

Solutions​

  1. Insufficient balance

    • Check balance with /balance
    • Earn more RSNC before claiming

  2. Perk sold out

    • Check availability with /perks

  3. Already claimed (max per user)

    • Some perks have per-user limits

  4. Perk doesn't exist

    • Verify perk_id is correct
    • Check /perks for valid IDs

Self-Hosted Deployment Issues​

Webhook Not Working​

  1. Verify URL is correct

    curl -X POST "https://api.telegram.org/bot<TOKEN>/getWebhookInfo"

  2. Check Worker is deployed

    • Cloudflare Dashboard → Workers
    • Verify deployment

  3. Check Worker logs

    • Cloudflare Dashboard → Workers → Logs

Environment Variables​

Ensure all secrets are set:

  • TELEGRAM_BOT_TOKEN
  • SUPABASE_PUBLISH_KEY
  • SUPABASE_SECRET_KEY

KV Namespace​

Ensure KV namespace is created and bound in wrangler.toml.

Getting Help​

  1. Check this guide first
  2. Review Partner Portal for configuration issues
  3. Contact support via Partner Portal
  4. Join Resonance Discord for community help
Last updated on