all Core tasks stop getting scheduled if there are more than 40 repos that need renaming

> [!NOTE]
> Migrated from [augurlabs/augur#3667](https://github.com/augurlabs/augur/issues/3667)
> Originally opened by `@cdolfi` on 2026-02-09

---

Once Augur is brought up Core tasks are only getting scheduled for the first few hours, I believe less than 12 but for sure less than 24 hours. Its usually about 1,500-3,000 repos that get through before it stops scheduling again. If you restart the containers the tasks get scheduled again and move as expected. I have been able to repeat this behavior multiple times.

Once this behavior was noticed on our instance all of our core repos were outside of the collection interval we have set. We still have about half of our repos outside the collection interval even with restarting it consistently the last few days.

My suspicion is that this bug was introduced in the last release

Update: this is happening at exactly 40 retries each time