Steps for troubleshooting the connection issue between Splunk On-Call and Slack.

Available Languages

Updated:September 30, 2026
Document ID:SPLK049781

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk On-Call

Description

When there is a breakage in the Splunk On-Call and Slack integration, and Slack is not sending alerts to Splunk On-Call, it is necessary to check the Slack Integration in Splunk On-Call. 


Resolution

When Slack is not sending alerts to Splunk On-Call, it is necessary to check the connection in Splunk On-Call for Slack Integration.

 

Please follow the steps below to open the Slack integration in Splunk On-Call:

 

Splunk On-Call > Integrations > Slack

 

If you see the Connection Lost message as shown in the image below, you need to click on Update Credentials to re-enable the connection with Slack.

 

NOTE: In order to Update Credentials you must have Global Admin and Slack Admin permissions.

 

slack error.jpg

 

Once the issue is fixed, you can send a test alert from Slack to Splunk On-Call and check if everything works fine.

Revision History

Revision Publish Date Comments
1.0
30-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

Related Articles