seeing a pretty big lag between the graphite checks page vs the corresponding github PR's checks. is this a known issue? any plans for improvement?
c
Chris Bowie
08/04/2026, 7:08 PM
Graphite’s Checks tab is a synced copy of GitHub’s checks, so it can trail what’s on the PR for a bit. If it usually catches up, that’s expected; if a PR stays wrong after a refresh, that’s something we want to dig into. Got a Graphite PR link where the lag is worst?
s
Sina Sabet
08/04/2026, 7:11 PM
Will link a PR next time I'm seeing it, but I experienced the following:
1. on graphite, checks show as failed for a branch
2. on graphite, click retry, button seems to have worked but UI still shows check as failed rather than transitioning to in-progress
3. on graphite, refreshing the page shows the check as still failed
4. in parallel, on github for the same PR, the check is being rerun and shows as in-progress
c
Chris Bowie
08/04/2026, 7:24 PM
That sequence matches a checks-sync issue after Graphite retry. When GitHub goes in-progress, our tab can stay failed through a refresh. When the rerun finished on GitHub, did Graphite eventually catch up?
If you need to unblock try a merge from GitHub or push a fresh commit. That usually gets it working again.
s
Sina Sabet
08/04/2026, 7:26 PM
I'm not blocked and things eventually sync up, but this in tandem with this other bug I've reported and am still experiencing means my experience on graphite is e2e quite flaky, and I have to often refresh and/or go to other surfaces to see if my clicks actually worked
Sina Sabet
08/04/2026, 7:26 PM
Can you clarify whether the lag is expected? This isn't like 5-10s lag, this seems more like "graphite shows the job as failed even though it's reexecuting until it's done", lag
c
Chris Bowie
08/04/2026, 8:10 PM
Hey There!
Usually its a few seconds to a minute, but not much longer than that. Next time you see it happen drop the PR link here and I can take a look at the backend while its happening.
Thanks!