Understanding add-on alerts
Add-on's alerts are typically triggered when Jive is having trouble communicating with the third-party add-on service. Some of the possible reasons are described in this topic.
Fastpath:
- Registry failure
- This alert can occur immediately after you first register Jive with the third-party
service if the external service is down or the certificate is failing. It could also occur
if you recently changed your
jiveURL
. You can try to re-register the service. If that doesn't resolve the alert, make sure the certificate and thejiveURL
are correct. - Configuration failure
- This alert can occur if your configuration information is incorrect. If you recently created or edited your configuration settings, verify that they are correct. A network-level communication problem could also cause this alert.
- Service call failure
- This alert can occur when Jive cannot reach the third-party service because the network is down, or because of some other communication issue. Jive tries to sync with the third-party service for seven days; after that, it stops trying and displays this alert. To resolve it, try fixing the underlying issue (typically a communication or configuration issue) and re-enable synchronization with the service.