Skip to main content

Fix Slack call/message log issues

Learn how to troubleshoot and resolve failed call and message logs from DialLink to Slack.

Updated today

Once you set up and configure the native integration between Slack and DialLink, you may occasionally receive email notifications that a call or message log could not be created automatically in Slack.

This can happen for several reasons. In this article, we’ll walk through the most common causes of failed call and message log syncs and how to resolve them.

How to resolve Slack call and message log issues

Authentication issues

Problem: The authentication token has expired, so DialLink can no longer access your Slack account.

Solution: Reconnect the integration by following these steps:

Permission issues

Problem: The access and permissions granted during setup have been revoked, so DialLink can no longer sync data with Slack.

Solution: Reconnect the integration by following these steps:

Configuration issues

Problem: Required fields are missing data during sync, or data is mapped to the wrong fields due to a system error.

Solution: Manually create or correct the call or message log in Slack using the details provided in the email notification.

If the issue persists, reconnect the integration:

Slack API limits exceeded

Problem: The Slack API request limit has been exceeded, preventing DialLink from syncing data.

Solution: Wait for the API quota to reset or increase your available API limits in Slack.

Manually add a call or message log to Slack

Call and message logs that fail to sync to Slack are not automatically re-synced after the issue is resolved. If you still need that information in Slack, you can add it manually using the details provided in the email notification.

Did this answer your question?