Fixed an automation job that had been overwriting the wrong project's description and logo for over a year

What happened

A job in the shared deployment templates keeps each project's description and logo up to date. It worked out which project to update by searching for its own name rather than using the project identifier it already had. Where two projects had similar names, the search returned the wrong one — and the job then overwrote that project's real description and logo.

Impact

Silent, ongoing data loss in the deployment system, present in both templates for more than a year and never noticed because the job always reported success. One project was confirmed corrupted from the job's own logs; a sweep of all 547 projects found three more collisions of the same class, of which one had already fired.

Resolution

The corrupted project's description and logo were restored from the original values. The job in both templates now uses the project identifier directly, which cannot resolve to the wrong project, so the remaining latent collisions can no longer fire.