Admin
Refresh schedule
Open issues are refreshed on every run (every 10 minutes). Separately, an hourly rotation picks exactly one project/source pair — whichever has gone longest without a full refresh (open + closed issues) — and fully refreshes it. This table shows that rotation order: the top row is up next.
| Project | Source | Last full refresh | Next full refresh | Full-refresh failures | Open-poll failures |
|---|---|---|---|---|---|
| snapcraft-rocks | github | (20 hours ago) | (up next) | 0 | 0 |
| starbase | github | (19 hours ago) | (in ~2 hours) | 0 | 0 |
| snapcraft (launchpad) | launchpad | (18 hours ago) | (in ~3 hours) | 0 | 0 |
| snapcraft | github | (17 hours ago) | (in ~4 hours) | 0 | 0 |
| craft-parts | github | (15 hours ago) | (in ~5 hours) | 0 | 0 |
| craft-platforms | github | (14 hours ago) | (in ~6 hours) | 0 | 0 |
| charmcraft | github | (13 hours ago) | (in ~7 hours) | 0 | 0 |
| craft-application | github | (12 hours ago) | (in ~8 hours) | 0 | 0 |
| craft-actions | github | (11 hours ago) | (in ~9 hours) | 0 | 0 |
| starflow | github | (10 hours ago) | (in ~10 hours) | 0 | 0 |
| rockcraft | github | (9 hours ago) | (in ~11 hours) | 0 | 0 |
| imagecraft | github | (8 hours ago) | (in ~12 hours) | 0 | 0 |
| debcraft | github | (7 hours ago) | (in ~13 hours) | 0 | 0 |
| craft-archives | github | (6 hours ago) | (in ~14 hours) | 0 | 0 |
| fetch-service | github | (5 hours ago) | (in ~15 hours) | 0 | 0 |
| craft-cli | github | (4 hours ago) | (in ~16 hours) | 0 | 0 |
| craft-grammar | github | (3 hours ago) | (in ~17 hours) | 0 | 0 |
| craft-providers | github | (2 hours ago) | (in ~18 hours) | 0 | 0 |
| craft-store | github | (1 hour ago) | (in ~19 hours) | 0 | 0 |
| craft-artifacts | github | (less than 1 hour ago) | (in ~20 hours) | 0 | 0 |