Skip to main content

Troubleshooting Intercom Reader

This topic lists common issues and quick checks to help you diagnose Intercom Reader problems.

  • Authentication failures (401/403): Verify the API key or OAuth access token, and confirm the app scopes include the tables you selected. If using OAuth with refresh tokens, ensure the tokens are current.

  • Invalid table names: Misconfiguration of Tables and Excluded tables can cause errors. Remove unsupported names or correct casing; use % wildcards carefully.

  • Conversations not readable: Reading Conversations may require specific Intercom plan/permissions. Exclude it or adjust your Intercom subscription and scopes.

  • No data in Incremental load: Check the Start position value (for example, %=-1 vs. a specific timestamp/offset) and confirm the Incremental load marker (UpdatedAt) is present and advancing.

  • Throughput or lag: Tune Thread pool count, Connection pool size, and Polling interval. Ensure thread pool does not exceed connection pool.