This document provides guidance for resolving common issues encountered during the implementation and operation of the Bromcom and Edlink integration. Each section highlights potential causes and solutions to ensure smooth functionality.
Missing Contacts
- Cause: Contact records in Bromcom may lack valid relationships or association metadata, which is not supported in Edlink's model.
- Resolution:
- Ensure all contact records in Bromcom have valid and complete relationship fields.
- Validate the data before syncing to Edlink to avoid filtering out incomplete records.
Partial Rosters
- Cause: Missing or incomplete user identifiers or metadata in Bromcom can prevent full synchronization.
- Resolution:
- Verify that all users in Bromcom have unique identifiers and roles assigned.
- Check API permissions to confirm access to all necessary roster data.
- Ensure the API credentials have been configured to retrieve full entity sets.
API Connectivity Issues
- Cause: Misconfigured API credentials, invalid tokens, or exceeding API rate limits can disrupt synchronization.
- Resolution:
- Ensure API credentials are correctly configured and authorized for the required scopes.
- Monitor API usage to avoid exceeding rate limits and retry sync operations as needed.
- Refresh or regenerate authentication tokens if they have expired.
This troubleshooting guide addresses common issues and resolutions for the Bromcom and Edlink integration. For further assistance, contact Edlink support.