timezone-butler
timezone-butler copied to clipboard
Bulter responds more than once on a trigger
Describe the bug The butler response posts several times
To Reproduce Steps to reproduce the behavior:
- Trigger timezone butler with any message about time (I only tried this in direct messages- did not want to spam a channel with multiple people so not sure if its reproducible in that setting)
Expected behavior The butler response only posts once
Screenshots
Additional context This happens at least with direct messages with the bot and direct messages with another user and a bot. I did not try in a channel since we felt the responses were too spammy.
We're seeing the same behavior in a channel, and it looks like there are at least two other duplicates of this issue submitted. Even more odd, it will post it one more time 6 min. later without additional activity in the channel. Just as shown in the screenshot.
Briefly looked into this, doesn't appear to be a time parsing issue. Potentially slack is sending multiple events per message because an ack
isn't sent back fast enough. Could not confirm this but wanted to jot down my findings.
Yeah I'm running it on a vercel free plan so it's definitely possible that it's slow enough for slack to send multiple events
I'm also seeing this behavior in our channel. I redacted the content of messages as this is a work Slack, and none of them mentioned time. I left the timestamps so you can see that there weren't any new messages in threads that might have generated this too.
What has been happening is it spams three times at first for any given time (in this case it was triggered by the "rest of the afternoon" message). This is the first time that I'm seeing it send a fourth message after the fact too.
I'm not an admin for this Slack area so I can't speak to any logs or anything like that that might be available, but I do know that it's not integrated across the entire Slack at our work... I had to request it for this channel. I'd like to get us to use it in more channels but right now with it spamming like this I can't in good consciousness promote its more widespread use sadly. :(
Hope this helps, if there's anything I can answer for you related to this let me know.
This is still happening in a Slack channel: