Confluence Unstructured Connector Limitations and Troubleshooting

The Confluence Unstructured connector ingests the following content types:

1. Pages (including nested/child pages)
2. Blog posts
3. Comments (on pages and blog posts)
4. Attachments (files attached to Confluence content)

Confluence Cloud Only

This connector supports Atlassian Confluence Cloud (SaaS) only. Confluence Data Center and Confluence Server are not supported.

Single Space per Data Lake Object

Each UDLO ingests content from a single Confluence space. To ingest content from multiple spaces, create separate UDLOs for each space.

The connector processes the following attachment file types from Confluence pages and blog posts:

Attachments with unsupported MIME types are skipped during ingestion.

Attachments are subject to the following size limits. Files exceeding these limits are skipped.

Outdated content is skipped to ensure data relevance.

Rule: Content older than two years relative to the current sync time will be skipped.

After the initial full ingestion, subsequent data stream refreshes use incremental sync.

• Only content created or modified since the last successful sync is processed.
• Deleted content in Confluence is automatically removed from the UDLO during incremental refresh.

When content fails any constraint check (format, size, or content age), it is skipped. The outcome is recorded in the UDLO.

Confluence Unstructured supports ingestion of spaces up to 500 GB per ingestion job.

Data stream refreshes that exceed 24 hours will time out. Plan ingestion jobs accordingly, especially for large spaces. If you encounter timeout failures, consider splitting content across multiple UDLOs by space to reduce per-job ingestion volume.

1. Verify the Cloud ID is correct by navigating to https://<your-domain>.atlassian.net/_edge/tenant_info.
2. Verify the Named Credential authentication was completed successfully by re-authenticating with the Confluence 3LO provider.
3. Verify the Admin API Token is valid and has not expired.
4. Verify the Org ID matches the organization associated with your Confluence instance.

If after a successful sync no records appear in the Data Lake Object:

1. Verify the Space ID is correct. The Space ID is case-sensitive (for example, ENG not eng). Check the URL: https://<domain>.atlassian.net/wiki/spaces/<SPACE_ID>/overview.
2. Verify content exists in the space. Empty spaces or spaces containing only restricted content will result in zero records.
3. Verify the authenticated user has read access to all content in the space, including restricted pages and blog posts.
4. Check content age. If all content in the space was last modified more than two years ago, all items are skipped due to the content age rule.
5. Check the UDLO Sync Status Detail field for individual record failure reasons.
6. Verify the Data Stream completed successfully. Navigate to the Data Stream and check for connector exceptions or partial failures.
7. For attachments: Verify the attached files use supported MIME types and are within size limits.

1. Large spaces may require additional sync cycles due to API rate limits.
2. Verify the authenticated user has permission to access all content in the space, including restricted pages.
3. Check the UDLO for skipped records. Some content may have been excluded due to file size, format, or content age rules.
4. If pages were recently updated but not appearing, wait for the next incremental sync cycle to complete.

See Also

• Salesforce Help: Data 360 Limits and Guidelines