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

[BUG] Discord - Reaction Added (Instant) duplicate events #3937

Closed
ctrlaltdylan opened this issue Aug 4, 2022 · 1 comment
Closed

[BUG] Discord - Reaction Added (Instant) duplicate events #3937

ctrlaltdylan opened this issue Aug 4, 2022 · 1 comment
Labels
bug Something isn't working tracked internally Issue is also tracked in our internal issue tracker triaged For maintainers: This issue has been triaged by a Pipedream employee

Comments

@ctrlaltdylan
Copy link
Contributor

Describe the bug
Whenever a reaction is added however, it receives two exact replica inputs and therefore triggers the workflow twice at the same time.

To Reproduce
Steps to reproduce the behavior:

  1. Create a Discord - Reaction Added (Instant) source
  2. Add a reaction to the relevant Discord channel
  3. See multiple invocations / events instead of one

Expected behavior
One reaction should result in one invocation.

Screenshots

https://i.gyazo.com/0c510593a40012d04655ea6897f400b9.png

Additional context

Community report - https://pipedream.com/community/t/reaction-added-instant-triggered-twice-instead-of-once-discord/2944

@ctrlaltdylan ctrlaltdylan added the bug Something isn't working label Aug 4, 2022
@js07 js07 added the tracked internally Issue is also tracked in our internal issue tracker label Aug 4, 2022
@dylburger dylburger added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Aug 4, 2022
@dylburger
Copy link
Contributor

This should be completed! Please let us know if you see any issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tracked internally Issue is also tracked in our internal issue tracker triaged For maintainers: This issue has been triaged by a Pipedream employee
Projects
None yet
Development

No branches or pull requests

3 participants