Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Slack Workflow messages that mention Junior are dropped

Open
  • Is something wrong?
#2,034 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
api, backend

Research direction

Start by reading packages/junior/src/chat/ingress/workspace-membership.ts and packages/junior/src/chat/ingress/slack-webhook.ts, then trace how Slack bot_message events with bot_id and no user are filtered and routed. The issue leaves open whether trusted Workflow Builder posts should trigger turns or scheduled automations should be the only supported path; resolve that decision before changing behavior. Done means the chosen behavior is explicit and a dropped mention no longer fails silently.

Written by the indexing model from the issue text.

Description

Since #1936 (merged 2026-09-25), Junior ignores Slack Workflow Builder posts that @-mention it. These posts are bot_message events with a bot_id and no user, and isSlackWorkspaceMember (packages/junior/src/chat/ingress/workspace-membership.ts) returns false when event.user is missing. The webhook then returns before the message is routed (packages/junior/src/chat/ingress/slack-webhook.ts).

Reported by Chuck Daminato.

Observed

  • A weekly Workflow posts "@Junior post upcoming holidays for VIE/YYZ/SFO/SEA in the next 2 weeks" every Monday at 12:00 UTC.
  • 2026-09-21 (before #1936): Junior replied on its own.
  • 2026-09-28 and 2026-10-05 (after #1936): no reply until a person mentioned Junior in the thread.
  • Even when Workflow runs did trigger a reply, they had no user credentials, so Junior couldn't read the linked Notion page and used public holiday calendars instead.
  • When a person then pinged the thread with "?", Junior asked for confirmation instead of acting on the Workflow's request, because it treated the bot message as background context.

Workaround in use
The holiday reminder was moved to a Junior scheduled automation (weekly, creator credentials). The old Workflow should be disabled.

Decision needed
Should trusted Workflow Builder posts in our workspace be allowed to trigger Junior turns again, or should scheduled automations be the only supported way to run recurring Junior tasks? Whichever we choose, a dropped bot mention currently fails silently. The person who set up the Workflow gets no signal that it stopped working.

via chuck.

--

View Junior Session [Sentry]

Dominant language
TypeScript
Stars
362
Forks
38
Avg merge
5h 9m
Merged PRs (30d)
166

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/junior

All issues in getsentry/junior

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.