WebEx Teams
| Error message | Likely meaning (TL;DR) | Recommended next steps |
|---|---|---|
| TypeError: Cannot read properties of undefined | Your Node.js handler is trying to read notificationAttributes from an object that is undefined (likely the incoming Webex payload doesn’t include the expected field/structure). | |
| Failed to open TCP connection to wbxwebhooks.joesjavajoint.com:443 | It means the system could not establish an HTTPS connection to wbxwebhooks.joesjavajoint.com on port 443, so that endpoint is currently unreachable | The destination URL, DNS, firewall/network access, and server availability/SSL configuration need to be checked. |
| 502 Bad Gateway | If you get 502 When posting to the Webex WebHook URL, it usually means the failure is upstream (Webex or an intermediate gateway/service on the Webex path) rather than a client-side validation error, | Retry and check Webex service status/support, while also confirming your request/payload is valid. |
| "errorCode":404,"message":"The requested resource could not be found." (trackingId ROUTERGW) | Webex returned 404 when Xyte tried to deliver the notification — the target Webex room/space or webhook no longer exists (it was deleted, archived, or the bot was removed from it). Not an authentication problem. | Verify the target Webex room/space still exists and the integration bot is still a member. Recreate or re-select the target room / webhook in the integration settings, then reconnect and send a test notification. |
Updated 5 days ago
What’s Next
Did this page help you?