Support

CodeDoc for Confluence

Get help

Have a question, found a bug, or want to request a feature? We're happy to help. Email us and we typically respond within 1–2 business days, or open a public issue on GitHub. Check the existing issues first: your question may already have an answer.

Before you reach out

Most questions are answered in the documentation: it covers setup, sync blocks, AI pages, Git and AI providers, webhooks, schedules and troubleshooting. Common ones:

• "the file or the branch does not exist (HTTP 404)": check the file path and the branch in the block settings. Paths are case-sensitive and start below the repository root; Show preview checks the path before you save.
• "the Git provider rejected the access token (HTTP 401)": the token stored in CodeDoc is invalid or expired. An administrator can replace it under Settings → Connections. The block keeps its last good content until the next successful update.
• "Settings incomplete" or "Waiting for approval": Settings incomplete lists the missing settings (edit the page, select the block and click the pencil icon). Waiting for approval means new or changed settings are not approved yet: a Job Operator or Administrator who can edit the page has to open it once.
• "On every push" does not update: push updates need the CodeDoc webhook with the secret from CodeDoc → Settings → Webhook in the repository (webhook setup) and a push to the branch the block follows; calls without the secret are rejected (the Git provider's delivery log shows HTTP 403). Update now checks the block in the meantime.
• "A Confluence page with this title already exists": page titles are unique per space. Rename the AI page, or rename or move the other page in Confluence.
• A scheduled AI page didn't run at the expected time: schedules are checked hourly, so a run starts up to about 1 hour after the configured time.

What to include in a bug report

• Your Confluence site URL
• Whether it is about a sync block or an AI page, and the exact message CodeDoc shows
• Easiest: the Report a bug button under Settings → Privacy & help creates a pre-filled email with diagnostic information
• What you expected vs. what you saw (a screenshot helps a lot)

Legal: Privacy Policy · Terms of Service · Security Statement