Title: Enabling Slack Error Notification – “Something went wrong”
Last modified: January 15, 2024

---

# Enabling Slack Error Notification – “Something went wrong”

 *  Resolved [Razorfrog Web Design](https://wordpress.org/support/users/razorfrog/)
 * (@razorfrog)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/enabling-slack-error-notification-something-went-wrong/)
 * When I enter my email and press “Continue to Slack” I see the error notice “Something
   went wrong”. No further details. How can I troubleshoot this connection?
 * I’ve tried in multiple browsers.
 * Thanks for any help

Viewing 1 replies (of 1 total)

 *  Plugin Support [Amimul Ihsan](https://wordpress.org/support/users/amimulihsanmahdi/)
 * (@amimulihsanmahdi)
 * [2 years, 4 months ago](https://wordpress.org/support/topic/enabling-slack-error-notification-something-went-wrong/#post-17353624)
 * Hello there,
   Thank you for letting us know. We have tested this, and it seems
   like that it is a possible bug. Our team will take a look and fix the issue soon.
 * Thank you

Viewing 1 replies (of 1 total)

The topic ‘Enabling Slack Error Notification – “Something went wrong”’ is closed
to new replies.

 * ![](https://ps.w.org/fluent-smtp/assets/icon.svg?rev=2458343)
 * [FluentSMTP - WP SMTP Plugin with Amazon SES, SendGrid, MailGun, Postmark, Google and Any SMTP Provider](https://wordpress.org/plugins/fluent-smtp/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/fluent-smtp/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/fluent-smtp/)
 * [Active Topics](https://wordpress.org/support/plugin/fluent-smtp/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fluent-smtp/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fluent-smtp/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Amimul Ihsan](https://wordpress.org/support/users/amimulihsanmahdi/)
 * Last activity: [2 years, 4 months ago](https://wordpress.org/support/topic/enabling-slack-error-notification-something-went-wrong/#post-17353624)
 * Status: resolved