Hi Graphite team, I'm experiencing an issue whe...
# report-bugs
l
Hi Graphite team, I'm experiencing an issue where one repository shows "missing permissions" even though the GitHub App is correctly configured: - Organization: lees-dev - Problem repo: medpure-insights - Working repo: FlowScribe (same org, works fine) - GitHub App: Installed with "All repositories" access - Personal account: Authorized (korallis) - Installation ID: 94146029 (updated 2025-11-12T010320.000Z) Both repos have identical settings (internal visibility, same permissions). FlowScribe detects fine, but medpure-insights shows missing permissions. Created PRs (#1, #2) to trigger webhooks - no change. Re-authenticated multiple times - no change. This appears to be a sync/database issue on Graphite's side. Can you manually trigger a sync for lees-dev/medpure-insights? Contact Graphite Support: - Email: support@graphite.dev - Or look for a chat widget on app.graphite.dev This is definitely not a configuration issue on your end - it's a Graphite bug
p
(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using
gt feedback --with-debug-context <any message>
l
everything you need is in the intial request
image.png
p
Hi Lee, thanks for the detailed report here. Typically this self resolves pretty quickly. One question for you re
Re-authenticated multiple times - no change.
have you tried to reset the app authentication in the app? or did you sign out and sign back in? Steps ive seen work to resolve this: • Log in to GitHub + SAML/SSO for the GitHub organization (if applicable) • Then in Graphite reset the app authentication in your GitHub authentication settings: The only other time ive seen this persist is when a user is an external contributor but im not sure that can be the case if the other repo shows fine. Let me know about the resetting Q above and ill look into what we can do re foced sync though im not sure its possible today.