Slack alarm notifications test fails with “invalid_token”

Verify that the notification destination URL is still active, check the expiration status of the destination token, or create a new webhook in the destination.

Written by david.vega

Last published at: November 6th, 2024

Problem

When creating a Slack notification destination, the destination test fails with an error. 

Request failed.

Response
invalid_token

 

Cause

The token was revoked on the notification Slack target. There are three reasons this happens. 

  • The webhook on the destination was deleted.
  • The token expired.
  • The token was directly revoked from the destination in use.

 

These factors disrupt the integration between Databricks and the destination, leading to the failure of the alarm notification.

 

Solution

  • Verify that the notification destination URL is still active and has not been deleted. If removed on the destination target, create a new one and update the alarm within Databricks with the new URL reference. 
  • Check the expiration status of the destination token. If expired, generate a new token.
  • For a revoked token, create a new webhook in the destination and update the Databricks alert configuration with the new webhook URL. 

 

After updating the webhook URL, reference or token, re-run the test for the affected alert to ensure the issue is resolved.

For detailed steps on managing and rotating webhook setup for Slack alerts, please refer to Slack’s Token rotation and auth.revoke documentation.