<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=395500) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=395500) </details> <!--IssueSummary end--> Investigation issue for https://gitlab.com/gitlab-org/gitlab/-/issues/364640#note_1305127314 ### Summary of problem: Pipeline artifact files are missing from Geo primary node during replication. ### Action Items Geo has [already](https://gitlab.com/gitlab-org/gitlab/-/issues/395500#note_2717585578) started working on making the migration process more fault-tolerant. From ~"group::pipeline execution"'s end we need to implement a health check mechanism to assist in tracking instance health. 1. Implement a [Service Ping](https://docs.gitlab.com/development/internal_analytics/service_ping/) worker to track instance usage for Dedicated and Self-managed instances 2. Communicate the new data to support.