Skip to content

handle app mention events for workspaces that don't deliver message.channels #12193

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.

Sign up for GitHub

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

Closed
yunyunyunyun-yun wants to merge 1 commit into from
Closed

handle app mention events for workspaces that don't deliver message.channels #12193

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions gateway/platforms/slack.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -184,12 +184,14 @@ async def connect(self) -> bool:
async def handle_message_event(event, say):
await self._handle_slack_message(event)

# Acknowledge app_mention events to prevent Bolt 404 errors.
# The "message" handler above already processes @mentions in
# channels, so this is intentionally a no-op to avoid duplicates.
# Handle app_mention events — fired when the bot is @mentioned in a
# channel. Some Slack workspaces only deliver app_mention (not
# message.channels) for @mentions, so we forward to the main
# handler here. The ts-based deduplicator in _handle_slack_message
# prevents double-processing when both events arrive.
@self._app.event("app_mention")
async def handle_app_mention(event, say):
pass
await self._handle_slack_message(event)

@self._app.event("assistant_thread_started")
async def handle_assistant_thread_started(event, say):
Expand Down