Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicates of events with different message_id #918

Open
PurpleHorrorRus opened this issue Mar 1, 2024 · 3 comments
Open

Duplicates of events with different message_id #918

PurpleHorrorRus opened this issue Mar 1, 2024 · 3 comments
Labels
product: eventsub EventSub (Webhooks and WebSockets)

Comments

@PurpleHorrorRus
Copy link

Brief description
When I subscribe to events using a webhook, I receive duplicate of event with different message_id. But when I started the test server using twitch-cli, there is no such issue. For example, I testing on channel.update endpoint, editing title and category on my Twitch page.

How to reproduce
Subscribe to channel.update using websocket, but it seems only me faced this issue.

Expected behavior
Single incoming event.

Screenshots
image

Additional context or questions
It also actual for other events like stream.online. I tried to delete all old subscriptions, but it didn't help.

@PurpleHorrorRus PurpleHorrorRus added the product: eventsub EventSub (Webhooks and WebSockets) label Mar 1, 2024
@Dkamps18
Copy link
Member

Dkamps18 commented Mar 1, 2024

Does this also happen to other categories? Tarkov has drops at the moment so it may be possible that the drops tag being added maybe causes the 2nd trigger even though its not in the payload

@PurpleHorrorRus
Copy link
Author

Does this also happen to other categories?

Yes, it doesn't depend on category.

@Dkamps18
Copy link
Member

Dkamps18 commented Mar 1, 2024

No clue than, weird one for sure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product: eventsub EventSub (Webhooks and WebSockets)
Projects
None yet
Development

No branches or pull requests

2 participants