Troubleshoot Confluence ingestion

This page describes common issues with the Confluence connector in Databricks Lakeflow Connect and how to resolve them.

For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.

Authentication errors

Error:

The user does not have access to the specified site 'https://your-domain.atlassian.net' with the given token, or the URL is incorrect. Please verify the URL and the OAuth token's permissions.

Resolution:

  1. Check the OAuth scopes granted in the OAuth app.
  2. Check that your Confluence instance URL is correct and includes the full domain (for example, https://your-domain.atlassian.net).

Rate limit errors

Error:

Confluence API rate limit exceeded.

Resolution:

  1. The Confluence connector automatically retries with exponential backoff when rate limits are encountered.
  2. If rate limit errors persist, consider scheduling pipeline runs during off-peak hours.
  3. For large Confluence instances, you might need to increase the time between pipeline runs.
  4. Contact Atlassian support if you need to increase your API rate limits.## Space not found errors

Missing pages or incomplete data

Issue: Some pages are not appearing in the ingested data, or the data appears incomplete.

Resolution:

  1. Verify that the pages exist in the source Confluence space and aren't archived. Archived pages aren't supported.
  2. Check that the pages aren't in a draft status. Only published pages are ingested.
  3. Confirm that the user account has read access to all of the pages in the space.
  4. Check the pipeline event logs for any warnings or errors related to specific pages.

Slow ingestion performance

Issue:

Pipeline runs are taking longer than expected.

Resolution:

  1. Initial pipeline runs (full snapshots) typically take longer than incremental runs.
  2. Large pages with extensive content or many attachments might slow down ingestion.
  3. Check if you're hitting Confluence API rate limits by reviewing the pipeline logs.
  4. If performance issues persist, create a support ticket.

Refresh token expiration

Issue:

The pipeline was working but suddenly started failing with authentication errors.

Resolution:

  1. Check the OAuth scopes granted in the OAuth app.
  2. Update the connection.
  3. Retry the pipeline.

Need more help?

If you encounter an issue that's not covered in this troubleshooting guide, create a support ticket.