A Webex Teams bot is deployed but soon it stops responding. Which two explanations are the cause of the issue? (Choose two.)

Question

Options

• AA new webhook was created, which marks the old webhook as inactive.
• BThe web server that is set to receive webhooks is not configured to return a 200 message. And the
• CThe webhook secret is expired and must be refreshed.
• DThe refresh token is not being used.
• EThe bot owner regenerated the access token on developer.webex.com.

• A
  43% (13)
• C
  13% (4)
• D
  7% (2)
• E
  37% (11)

Explanation

A is correct because Webex automatically deactivates older webhooks when a new one is created for the same resource/event combination - the bot silently stops receiving events with no error.

B is correct because Webex interprets anything other than a 200 OK response as a delivery failure; after repeated failures, Webex marks the webhook as inactive and stops sending events entirely.

C is wrong because webhook secrets in Webex do not expire - they are static HMAC signing keys used to verify payload authenticity, not time-limited credentials. D is wrong because bots use long-lived bot tokens, not OAuth refresh tokens (those apply to user integrations). E is wrong because bot access tokens are permanent and tied to the bot account itself - only a human user's token would be regenerated on the developer portal.

Memory tip: Think of the two ways a webhook goes "silent" - it gets replaced (A) or it gets ignored (B). Both result in Webex quietly disabling the webhook; the bot isn't broken, its delivery channel is.

No community discussion yet for this question.