A bridge-maintenance ChatOps bot must react when someone types /fail-over in the ops Webex space. Which construction avoids polling GET /messages?
Select an answer to reveal the explanation.
Short Explanation
Don’t keep opening the mailbox every second—leave a doorbell (webhook) for new messages. Register messages/created with a public targetUrl and usually a roomId filter for that ops space.
Full Explanation
Reactive ChatOps registers a Webex webhook for resource messages and event created, with a reachable targetUrl and typically a roomId filter so only the ops space fires. Polling GET /messages is the anti-pattern. Pagination of history is a Domain 2 concern, not the event-driven ChatOps construction.