Vitally health score split across two records duplicate external_id error on trait sync for merged accounts
Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Use when you see this exact failure in Vitally and the affected record or object can be named. Not for a different Vitally error with another message, or for general setup with no failure present.
TL;DR
Fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Start in the Vitally account list, the trait sync log, and the health score config, work on one affected item, and prove the fix there before running the full set. Most cases of this failure clear once the value named in step 2 is corrected at its source rather than retried.
Vitally health score split across two records duplicate external_id error on trait sync for merged accountsUse this when
- You see this exact message or symptom in Vitally: Vitally health score split across two records duplicate external_id error on trait sync for merged accounts
- One run, record, build, or object is affected and you can name it
- A retry without changing anything reproduces the same text
Not for this skill when
- Vitally fails with a different message and none of the signals here appear
- Nothing has failed yet and you are doing first time setup or general planning
- Every service from this vendor is down for all users, which is a vendor outage to wait out first
Steps
- Reproduce the failure once in the Vitally account list, the trait sync log, and the health score config and search the log or history for the exact text in the block above, recording the time, the workspace or project, and the one object it names. Verify: you have one failing run or object identified, not a similar older failure
- Inspect the external_id mapping for merged accounts, the trait source, and the score segmentation rules, and check the existing object id, the fields that differ between the copies, and the merge or update decision recorded for it. Verify: you can point to the specific value, field, or identity that does not match what this operation needs
- Apply the fix at that source: fetch the existing object first and update it in place, or merge the duplicates and keep the record with the fuller history, instead of creating a second one. Verify: the corrected value or setting is visible in Vitally itself, not only in a local config file
- Re-run the original operation on the single affected item first: re-sync traits for the merged accounts, merge the duplicate Vitally records, then recalculate scores. Verify: that one item completes with no trace of the error text from the block above
- Check the downstream result a user or the next job would see: one Vitally record per account with the combined usage history and a single health score. Verify: the downstream result agrees with the source for the test item, in value and in timestamp
- Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the error and the changed setting, and no earlier item regressed
Variant phrasings
Vitally health score split across two records duplicate external_id error on trait sync for merged accounts
The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the object the log names.
Vitally version of this failure
The tool-first phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.
Why does vitally health score split across two records duplicate external_id error on trait sync for merged accounts keep happening after a retry
The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the object state, not in the attempt.
Compatibility: Vitally traits and health scores, CRM and product usage integrations. The steps assume you can read the job or build log and change the named object in Vitally.
Why it happens
In Vitally, this failure usually means a create was issued for something that already exists under the same name, id, or key, so the service refused it or counted it twice. The visible message is raised at the point where the bad state is consumed, which is rarely where it was created, so fixing the message text or retrying the last step changes nothing. Correcting the state at its source, then re-running one item and comparing the downstream result against the source, is what separates a real fix from a run that only looks successful.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst58ADZFv8qrMaeowhL-zDA