Failed repositories on the source page
Version: 3.2.0 Date: 2026-11-17
Goal: After a migration, one Git source can hold hundreds of repositories. A single webhook failure marked the whole source Disconnected, so the operator could not see which repositories to remove.
Solution: The init report is read per repository. The source stays connected while at least one repository succeeded. Failed repositories are shown on the source page and in edit, where each one can be removed.
Features:
- Source page lists failed repositories in a card grid, with a Failed badge and the init error on hover
- Failed only hides the repositories that initialized
- Edit shows the same failures and a trash icon at the end of the row
- The source is Disconnected only when every reported repository or path failed
- Hourly discover and Check now skip a fully disconnected source, and skip only the failed FTP paths when the source is still connected
Files Modified:
src/core/data/data.service.ts- disconnect rule is per init unitsrc/protocol/source/ftp/ftp.service.ts- skip failed pathssrc/protocol/source/email/email.service.ts- skip a failed mailboxui/src/pages/workflows/- source page, edit table, connection badgeui/src/protocol/tower.mock.ts- demo GitLab repositories in failureui/src/shared/theme/joyTheme.ts- orange and neutral shades used by chips and filtersdocs/user/configuration/sources.md- failed repositories (EN and FR)docs/user/operations/troubleshooting.md- how to remove them (EN and FR)package.json-follow-redirects1.16.1 andpicomatch4.0.7.snykandui/.snyk- ignore the picomatch advisory that has no patched release, until 2027-01-20
Release fragment: feat-failed-repositories