Confluence Cloud

​

Common issues

• Verify Client ID and Client Secret are correct — no extra spaces
• Check that the OAuth app is active in Atlassian Developer Console
• Regenerate the secret if necessary and update PipesHub

• Ensure the Redirect URL in PipesHub exactly matches the Callback URL in Atlassian
• Check for trailing slashes, protocol differences (http vs https), or casing
• Update both configurations to use the same URL

• Confirm the token was copied correctly — no leading/trailing whitespace
• The token may have been revoked or expired; create a new one at id.atlassian.com/manage-profile/security/api-tokens
• Verify the Email field matches the Atlassian account that created the token
• Verify the Base URL matches your Confluence site (must include https:// and match *.atlassian.net)

• Must include the protocol: https://
• Must match the actual Confluence Cloud site (usually *.atlassian.net)
• A trailing slash or a trailing /wiki is fine: https://acme.atlassian.net/wiki works the same as https://acme.atlassian.net
• Do not include longer paths like /wiki/spaces/...

• Credentials rejected (401): check the email and API token, or reconnect the OAuth app
• Missing OAuth scopes: the message names the missing scopes. Add them to the app in Atlassian Developer Console, then reconnect
• Can’t read Confluence (403): the account signed in but has no Confluence access. Give it Confluence access and permission to view the spaces to sync
• No site found (404): no Confluence site at that URL. Use the form https://yourcompany.atlassian.net
• Site unreachable: Confluence did not answer. Check the URL, or try again in a few minutes

• When a sync ends with anything that failed, partial failures included, PipesHub sends one notice to the connector’s creator and the org admins listing what didn’t finish. Successful syncs send nothing
• A scheduled or startup sync that can’t start also sends a notice
• A lasting condition, such as no access to the audit log, is reported when it first appears, not on every sync

• The connector paces its requests (at most 10 per second with an API token, 6 per second with OAuth) and retries rate-limited requests, waiting as long as Atlassian’s Retry-After header asks
• If the OAuth app’s hourly quota runs out, the sync stops cleanly and the notice says when the quota resets. The next sync resumes from the last saved batch. Until then, opening a record’s preview returns 429 with a Retry-After header

• Verify you’re signing in with an account that has Confluence access
• Ensure your Confluence site is selected during authorization
• Check that all required API scopes are configured

• Verify the connector status shows Active
• Check that the authenticating user (OAuth) or token-owning user (API Token) has access to Confluence spaces
• Ensure spaces are not restricted or archived
• Review sync logs for specific error messages

• OAuth tokens may expire per Atlassian’s policies; disable and re-enable the connector to re-authenticate
• API tokens can be revoked from the Atlassian account page; generate a new one and update the Authenticate Instance tab
• Check if the OAuth app is still active in Developer Console

• Verify the authenticating user has read access to the content
• Check space permissions in Confluence
• Review page restrictions that may limit access

​

Initial sync

• Fetches all accessible content from connected Confluence spaces
• Indexes pages, blog posts, attachments, and comments
• Respects user permissions for content visibility
• Duration depends on the size of your Confluence workspace

​

Incremental sync

• Uses timestamp-based synchronization to detect changes
• Only syncs new or modified content since last sync, plus current pages and blog posts that PipesHub doesn’t hold (see Deleted, trashed and hidden content)
• Each sync also re-checks the 24 hours before the previous sync, so edits made around then aren’t missed. This look-back never goes earlier than a Modified Date Is After date you set
• Syncs every attachment of a page or blog post, however many it has. If the attachment list can’t be read in full, the attachments already read are kept, and the space’s page or blog post checkpoint doesn’t move, so the next sync reads that time window again. That includes a temporary failure (such as a timeout or rate limit) on the list’s first request, in which case the connector uses the attachments that came with the page or blog post in the search results. If the first request fails for a lasting reason, such as the list not being found, the connector uses those search-result attachments and the checkpoint moves on as usual
• Reduces API calls and sync duration
• The sync point moves only after each batch is saved, so a sync that stops early resumes from the last saved batch

​

Comments

• Pages and blog posts are indexed with their footer and inline comments inside the page, not as separate items. The Index Page Comments and Index Blogpost Comments settings control whether comments are included
• A new or edited comment re-indexes its page or blog post
• Pages indexed before this format switch to it when they next change; there is no mass re-index

​

Completeness

• Deleted attachments and deleted folders are removed
• Attachments added or updated on a page that itself didn’t change are picked up
• A full sync that couldn’t read part of Confluence removes nothing, and the next sync retries it once
• A space that fails doesn’t stop the sync of other spaces
• Images too big to inline in the page are kept as separate file records

​

Deleted, trashed and hidden content

• Deleted or hidden in Confluence: a stored page or blog post missing from that list is removed from PipesHub, with its file attachments, comments and replies. That covers content that was deleted, moved to the trash or out of the space, or restricted so the account can’t see it.
• Kept: archived pages the account can see. When a page or blog post is removed, the folders and child pages directly under it stay, and PipesHub lists them at the top of the space.
• Coming back: each incremental sync also fetches, by ID and within your sync filters, the current pages and blog posts in that list that PipesHub doesn’t hold, whatever their last-modified date. Content the account can see again returns on the next sync.
• Spaces: a space the account can no longer see, or that the space filter now leaves out, is removed with its records. If it comes back, it is read in full.
• When Confluence can’t be read: if a space’s list can’t be read to the end, or PipesHub can’t read what it has stored for that space, nothing is removed for that space and content type, and its checkpoint doesn’t move. A space list that can’t be read to the end, or that comes back with no spaces at all, removes no space.
• When a removal fails partway: removal runs in order: the folders and child pages move to the top of the space, then the file attachments, comments and replies are deleted, then the page or blog post itself. Whatever was done before a failure stays done. For example, if the page itself can’t be deleted, its attachments and comments are already gone; if one attachment can’t be deleted, those deleted before it stay deleted. The space’s other removals for that content type still go ahead, but that type’s checkpoint doesn’t move, so the next sync retries whatever is still stored. Other spaces and the other content type carry on.

​

Permission handling

• Syncs content based on the authenticating user’s permissions
• Each user sees only content they have access to in Confluence
• Respects space permissions and page restrictions
• Maintains Confluence’s access control model
• Attachments and comments of a restricted page are restricted the same way as the page. When a page becomes restricted, or stops being restricted, its stored attachments and comments (and their replies) follow
• A page restricted to a group PipesHub hasn’t synced yet stays restricted; the group’s members get access once the group syncs and the page is read again
• If a space’s permissions, a group’s members, or a page’s restrictions can’t be read for a temporary reason, PipesHub keeps what it already has and tries again on the next sync. A failed read never opens a page to its whole space and never removes access
• Restriction changes are found from the audit log. If the audit log can’t be read (the account isn’t a Confluence admin, or the OAuth app lacks read:audit-log:confluence), they are found by re-checking the page, blog post and folder listings instead
• Restrictions are read in full, including those with more than 100 users or groups
• Groups deleted in Confluence and users removed from the site lose access
• Guests and external collaborators are marked as guests
• “All licensed users” and admin space permissions map to the matching Confluence groups, not to the whole organization. Anonymous access to a space gives everyone in the organization read access
• Space permissions of users whose email is hidden are kept
• A page moved without a new version gets its new parent and access

​

Known limits

• An attachment deleted without a page edit stays until the page changes or a full sync runs, because Confluence search doesn’t return deleted content. Deleted comments behave the same way
• A page restricted to a group created during a sync gets that group’s access when the page next changes
• Atlassian returns at most 10,000 users from its user list. Users past that limit are not synced, and the sync notice says so

1. Email mismatch - The email used during connector authentication doesn’t match your PipesHub account email. This causes permission issues preventing you from accessing synced data.
   • Fix: Reconfigure the connector and authenticate using the same email as your PipesHub account.
2. Records show in “All Records” but not in search - Documents display in the All Records section but don’t appear in search query results.
   • Fix: Verify sync filters in the connector settings and ensure indexing has completed. Check that the data matches your search query criteria.
3. Data not yet indexed - The connector is still syncing or hasn’t completed the initial indexing process.
   • Fix: Go to Settings > Connectors, check the sync status, and wait for indexing to complete.

1. Create a dedicated connector instance — Create a Confluence connector instance for the space that contains the pages you want to index.
2. Select Manual Indexing — When configuring the connector, choose the Manual Indexing option. This gives you granular control over which content gets indexed.
3. Select the Confluence space — Use the filters to select the specific Confluence space that contains the pages you want to index.
4. Navigate to specific pages — Go to All Records in the navigation bar, then browse to the specific pages you want to index within the selected Confluence space.