Opened 2 years ago

Last modified 22 months ago

#6405 new task (blessed)

Migrate the `/here` command to use the Slack Messaging API

Reported by: dd32's profile dd32 Owned by:
Milestone: Priority: high
Component: Communication (Matrix, Slack, IRC) Keywords:


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_url url, which updates the Processing... message to Done! Your announcement has been made or Sorry, 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).

Change History (3)

This ticket was mentioned in Slack in #meta by dd32. View the logs.

2 years ago

#2 @dd32
23 months ago

Partially related #6116

This ticket was mentioned in Slack in #meta by shetheliving. View the logs.

22 months ago

Note: See TracTickets for help on using tickets.