slackapi / slackapi/bolt-js

Feature Request: manual ack option

Open
#2,788 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auto-triage-skip enhancement semver:major
Dominant language
TypeScript
Stars
2.9k
Forks
446
Avg merge
1d 3h
Merged PRs (30d)
28

Description

Feature

It would be nice if bolt provides an option to manually send an ack by user.
Currently, bolt automatically sends an ack for the Events API requests.
https://github.com/slackapi/bolt-js/blob/e35ca5ca562213c804cd443d2117c02620e69272/src/App.ts#L1173-L1175

Purpose

I use the socket mode client (@slack/socket-mode) for development in the multiple environments. My client sends an ack only if the message is for the corresponding environment.

For example,

  • For the permanent environment, the client sends an ack if it receives a message without any prefix. e.g., @app Hello
  • For an ephemeral environment, the client sends an ack if it receives a message with the prefix. e.g., [pr-123] @app Hello

In my experience, we should not use this pattern for permanent environments, because it causes a message delay. Slack retries to send a message until any client sends an ack.

I think this pattern is still useful if we want to test the client in an ephemeral environment.

Contributor guide

Open the contributing guide

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.

Research direction

Start in src/App.ts at lines 1173-1175, where Bolt automatically acknowledges Events API requests, and read the surrounding request-handling flow. Determine how a manual acknowledgement option would affect the socket mode client described in the issue. Done means users can choose manual acknowledgement while the existing automatic behavior remains available.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.