Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: Twitch plugin: provider exits immediately after startup (auto-restart loop) — same pattern as #26478 (LINE) [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#60071•Fetched 2026-04-08 02:36:48
View on GitHub
Comments
1
Participants
1
Timeline
1
Reactions
0
Author
nhaenernhaener
Participants
nhaenernhaener
Timeline (top)
commented ×1

Error Message

Twitch │ ON │ WARN │ Account has never connected successfully

Code Example

{
  "channels": {
    "twitch": {
      "enabled": true,
      "accounts": {
        "default": {
          "username": "my_bot",
          "accessToken": "${TWITCH_ACCESS_TOKEN}",
          "clientId": "${TWITCH_CLIENT_ID}",
          "channel": "my_channel",
          "requireMention": false,
          "allowFrom": ["<user_id>"]
        }
      }
    }
  }
}

---

info  twitch  Registered client manager for account: default
info  twitch  Using StaticAuthProvider for my_bot (no clientSecret provided)
info  twitch  Set up handlers for my_bot:my_channel
info  twitch  Connected to Twitch as my_bot
info  gateway/channels/twitch  [default] auto-restart attempt 1/10 in 5s

---

Twitch │ ON │ WARN │ Account has never connected successfully
RAW_BUFFERClick to expand / collapse

Twitch Plugin Bug Report — 2026-04-02

Title: Twitch plugin connects successfully but health monitor triggers restart loop

Version: OpenClaw 2026.4.2 (d74a122) Platform: Raspberry Pi 5, Linux 6.12.75+rpt-rpi-2712 (arm64), Node 24.13.0

Description: Twitch channel connects to IRC successfully but the health monitor immediately triggers an auto-restart loop. The connection never stabilizes — it cycles through all 10 restart attempts with exponential backoff.

Config (simplified):

{
  "channels": {
    "twitch": {
      "enabled": true,
      "accounts": {
        "default": {
          "username": "my_bot",
          "accessToken": "${TWITCH_ACCESS_TOKEN}",
          "clientId": "${TWITCH_CLIENT_ID}",
          "channel": "my_channel",
          "requireMention": false,
          "allowFrom": ["<user_id>"]
        }
      }
    }
  }
}

Log pattern (repeats until attempt 10/10):

info  twitch  Registered client manager for account: default
info  twitch  Using StaticAuthProvider for my_bot (no clientSecret provided)
info  twitch  Set up handlers for my_bot:my_channel
info  twitch  Connected to Twitch as my_bot
info  gateway/channels/twitch  [default] auto-restart attempt 1/10 in 5s

Time between "Connected" and "auto-restart": ~2ms

What we've tried:

  • Token with and without oauth: prefix
  • Flat config and accounts block format
  • Fresh tokens from twitchtokengenerator.com
  • openclaw doctor (no Twitch issues flagged)
  • Bot account is modded in channel
  • Channel name verified via Twitch UI

openclaw status shows:

Twitch │ ON │ WARN │ Account has never connected successfully

Expected: Connection stays up after "Connected to Twitch" log Actual: Health monitor immediately restarts despite successful IRC connection

Likely related: Issue #26478 (LINE plugin: provider exits immediately after startup, auto-restart loop). The LINE plugin had the same symptom — startAccount() resolved immediately instead of staying pending, causing the channel supervisor to auto-restart in a loop. This was fixed for LINE in 2026.4.1 but the same fix appears to not have been applied to the Twitch plugin.

Submit to:

GitHub Issues: https://github.com/openclaw/openclaw/issues/new Reference: https://github.com/openclaw/openclaw/issues/26478

extent analysis

TL;DR

The Twitch plugin's health monitor triggers an auto-restart loop immediately after connecting to Twitch, likely due to the startAccount() method resolving immediately instead of staying pending.

Guidance

  • Review the Twitch plugin's implementation to ensure it follows the same fix applied to the LINE plugin in version 2026.4.1, which prevented the auto-restart loop by keeping the startAccount() method pending.
  • Verify that the startAccount() method in the Twitch plugin is not resolving immediately, causing the health monitor to trigger the auto-restart loop.
  • Check the plugin's code for any differences in handling the connection state compared to the LINE plugin.
  • Consider applying a similar fix to the Twitch plugin as was done for the LINE plugin in issue #26478.

Example

No code snippet is provided as the issue does not contain sufficient code details to create a minimal example.

Notes

The provided information suggests a similarity between this issue and issue #26478, which was fixed for the LINE plugin. However, without access to the Twitch plugin's code, it's uncertain whether the same fix will apply.

Recommendation

Apply a workaround by modifying the Twitch plugin's code to keep the startAccount() method pending, similar to the fix applied to the LINE plugin in issue #26478, as this is likely to prevent the auto-restart loop.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#output truncation#response parsing#generation error#database connection#vector store

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING