Suggestion: Prevent duplicate messages by offering an optional post ID field

[r-cohen]

Description

Whether we are using the API from a client or server application, it may happen that the application using the slack API successfully sent a message, but that the connection got interrupted during the request, thus resulting in the application considering the post as a failure even though the slack API received and processed the request successfully. Usually, in case of failures, applications often perform retries (with back-off policy), this can result in duplicate messages. To avoid this, a new optional field can be added to the slack API, and if there is already a message posted with this ID, then the API could result in a 409 status code result instead of re-posting the msg.

What type of issue is this? (place an x in one of the [ ])

• [ ] bug
• [x] enhancement (feature request)
• [ ] question
• [ ] documentation related
• [ ] testing related
• [ ] discussion

Requirements (place an x in each of the [ ])

• [x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
• [x] I've read and agree to the Code of Conduct.
• [x] I've searched for any related issues and avoided creating a duplicate issue.

---

Bug Report

Filling out the following details about bugs will help us solve your issue sooner.

Reproducible in:

Development environment:

Steps to reproduce:

Expected result:

What you expected to happen

Actual result:

What actually happened

Attachments:

Logs, screenshots, screencast, sample project, funny gif, etc. If attaching logs, please remove user data and tokens.