Atlan Sync Failed: 2085654834

Metrics dictionary sync to Atlan has failed after 2 retries.

Aim to fully resolve this with 2-3 business days.
If the issue can't easily be resolved within a few hours, then:
- Post this issue in the #data slack channel, letting stakeholders know that event & metric definitions may be inaccurate in Atlan until the issue is resolved and that metrics.gitlab.com is still an accurate source of information.
- Once resolved, comment on the thread in #data and react with ✅.

As a first step, check the error message at the end of the job log.
Review the job logs for Failed POST / Failed GET / Failed PUT / Failed DELETE. Request failures are not expected and may indicate where the problem is occurring.
Run the sync locally against the Atlan POV instance.

A field was added/removed/changed in event/metric definitions.
- Solution: Field info may need to be updated in Atlan::Config::MetadataFields.
A new event/metric definition is misconfigured or missing required attributes.
- Solution: Fix the definition at source & redeploy.
An asset was modified in Atlan and is no longer compatible with the same API requests.
- Solution: Delete the asset in Atlan & retry sync.
Atlan unintentionally introduced breaking changes to their APIs.
- Solution: If it's possible without presenting inaccurate data in Atlan, take mitigating steps to unblock the rest of the sync and wait it out. Atlan has previously fixed bugs like this within a week or so. Otherwise, the changed API will simply need to be accomodated in the sync script.
GitLab categories or stages fixtures from other projects have been modified with incorrect formats.
- Solution: Accommodate the new format from ProductApi. Even if the fixture content is unexpected, we should keep it from causing the sync to error out. If the fixture content itself is incorrect, raise an issue with the team who originated the change.