Subject: Bug Report: channel.follow v2 EventSub WebSocket Not Sending Notifications Subject: Bug Report: channel.follow v2 EventSub WebSock
i dont know where i can post this but i just want to report this
Subject: Bug Report: channel.follow v2 EventSub WebSocket Not Sending Notifications
Subject: Bug Report: channel.follow v2 EventSub WebSocket Not Sending Notifications
Dear Twitch Developer Support,
I am reporting a bug in the EventSub API where channel.follow v2 subscriptions over WebSocket are not delivering notifications, despite being correctly configured and enabled.
SUMMARY
When subscribing to channel.follow events via WebSocket transport, the subscription is created successfully and shows status "enabled" in the API. However, no notifications are received when users follow the channel. In contrast, other EventSub subscriptions (such as channel.chat.message) on the same WebSocket connection work correctly.
TEST ENVIRONMENT
Bot Account:
- Username: mupongpongbot
- User ID: 1535275845
- Role: Moderator of target channel
Broadcaster Account:
- Username: musicfortheworld__
- Broadcaster ID: 1536964012
Test Account Used for Follow:
- Username: musicrelaxationandhealing (brand new account, never followed before)
- User ID: 1539409101
OAUTH SCOPES
The bot's OAuth token includes these relevant scopes:
- moderator:read:followers ✓
- moderator:read:moderators ✓
- moderator:read:chatters ✓
- user:read:chat ✓
- user:write:chat ✓
- user:bot ✓
STEPS TAKEN
Created EventSub WebSocket session
- Session ID: AgoQDh0I7VS6Saar41kPxTTWhRIGY2VsbC1h
- Status: Connected ✓
Subscribed to channel.follow v2 with correct conditions:
json
{
"type": "channel.follow",
"version": "2",
"condition": {
"broadcaster_user_id": "1536964012",
"moderator_user_id": "1535275845"
},
"transport": {
"method": "websocket",
"session_id": "AgoQDh0I7VS6Saar41kPxTTWhRIGY2VsbC1h"
}
}
API Response confirms subscription is enabled:
Type: channel.follow
Version: 2
Status: enabled
Transport: websocket
Session ID: AgoQDh0I7VS6Saar41kPxTTWhRIGY2VsbC1h
Condition: broadcaster_user_id=1536964012, moderator_user_id=1535275845
Verified channel.chat.message works on same WebSocket:
json
{
"metadata": {
"message_type": "notification",
"subscription_type": "channel.chat.message",
"subscription_version": "1"
},
"payload": {
"event": {
"broadcaster_user_id": "1536964012",
"chatter_user_id": "1539409101",
"message": {"text": "232323"}
}
}
}
Had test account (musicrelaxationandhealing) follow the channel
Confirmed follow was recorded in API:
GET /helix/channels/followers?broadcaster_id=1536964012
Response shows: musicrelaxationandhealing is now a follower with followed_at timestamp
Expected: WebSocket notification for channel.follow event
Actual: No notification received
VARIATIONS TESTED
✓ Tested with brand new account (never followed before)
✓ Tested after waiting 10+ seconds for subscription to propagate
✓ Tested removal of moderatoruserid → API rejected with "moderatoruserid failed on 'required' tag"
✓ Tested on same WebSocket session that successfully receives chat messages
✓ Verified follow exists in /helix/channels/followers endpoint
✓ Confirmed bot is moderator of channel
✓ Confirmed bot is follower of channel (in followers list)
ISSUE DETAILS
The problem appears to be one of the following:
WebSocket Limitation: channel.follow v2 EventSub notifications may not be supported over WebSocket transport, despite the API allowing subscriptions to be created.
Parsing Bug: Twitch may be sending follow notifications that TwitchLib is not parsing correctly.
Permission Issue: There may be an undocumented permission requirement or condition preventing notifications from being sent.
REQUEST
Could you please:
- Confirm whether channel.follow v2 notifications are officially supported over WebSocket transport
- Investigate why the subscription shows "enabled" but never delivers notifications
- Clarify if there are any known limitations or bugs with channel.follow v2 WebSocket subscriptions
- Suggest whether REST webhooks are required for channel.follow events instead of WebSocket
Thank you for your assistance in investigating this issue.
Best regards
This forum is for feature requests and suggestions. Please report bugs to https://github.com/twitchdev/issues/issues