# Renamed and moved repositories no longer stall jobs

Source: https://sengi.run/changelog/2026-11-17-renamed-and-moved-repositories-no-longer-stall-jobs

By Sengi · Published Nov 17, 2026

## What changed?

A repository that is renamed, recreated under its old name, or moved to another GitHub installation in the same Sengi project is now matched correctly. A repository that still conflicts is set aside on its own and the rest of the installation keeps running.

## Details

Sengi now applies an installation's repository list as one complete update, with renames applied before name checks. A repository moved to another installation in the same Sengi project is transferred: its old record keeps its jobs and billing history, and the receiving installation records the repository again with new consent and an empty cache.

A repository whose name or identity is held by another project is never claimed. It is set aside and logged by itself, where before it could hold the whole installation. If a repository still does not receive jobs after a rename or move, see the troubleshooting page.

## Related pages

- [Troubleshooting](https://sengi.run/docs/troubleshooting)

## More changes

- Next: [Spending cap: stop new jobs at a monthly amount](https://sengi.run/changelog/2026-11-17-spending-cap-stop-new-jobs-at-a-monthly-amount) (Nov 17, 2026)
- Previous: [Refreshed alternatives, cheapest-runners and pricing guides](https://sengi.run/changelog/2026-11-17-refreshed-alternatives-cheapest-runners-and-pricing-guides) (Nov 17, 2026)
- [All changes in the Sengi changelog](https://sengi.run/changelog)
