Opened 4 years ago
Last modified 4 years ago
#6405 new task (blessed)
Migrate the `/here` command to use the Slack Messaging API
| Reported by: | dd32 | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Communication (Matrix, Slack, IRC) | Keywords: | |
| Cc: |
Description
Due to some Slack API changes, it's not uncommon for the /here API to take more than 3,000ms between the API being called, and the response being sent.
This results in errors shown in slack to the user of:
/here failed with the error "operation_timeout"
This is both confusing, and bad UX.
Slacks APIs have changed to include a response_url webhook in the slash webhook payloads.
- Slack sends webhook
- We respond instantly with a 200, and a
Processing...message - We process the data, crunch the numbers, send announcements
- We make a webhook call to Slack on the
response_urlurl, which updates theProcessing...message toDone! Your announcement has been madeorSorry, you can't use /here here, but you can use it in ....error.
This change in flow will result in the slack user not seeing the operation_timeout error, and avoid needless confusion (Since the announcement is made, usually just after the timeout).
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Partially related #6116