You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a new co-working session is started, many times the zoom-meeting-webhook-handler triggers the meeting.started event twice. Then, when the session is ended, the meeting.ended event is triggered once for the second post in #co-working-room.
Steps to Reproduce
It happens randomly, but evidence of the issue can be seen by scrolling through the #co-working-room Slack channel history.
The text was updated successfully, but these errors were encountered:
I am making some assumptions here but I have seen this similar issue when using the slack buttons in messages. The response back from the server needs to happen within 3 seconds or slack will retry, resulting in doubling messages (https://api.slack.com/interactivity/handling#acknowledgment_response). I have seen this issue happen when using a function as a service (like AWS lambda) where the cold start time of the container exceeds the wait time for the slack messages.
What Happened?
When a new co-working session is started, many times the
zoom-meeting-webhook-handler
triggers themeeting.started
event twice. Then, when the session is ended, themeeting.ended
event is triggered once for the second post in #co-working-room.Steps to Reproduce
It happens randomly, but evidence of the issue can be seen by scrolling through the #co-working-room Slack channel history.
The text was updated successfully, but these errors were encountered: