Skip to main content
All CollectionsFAQ
Why do my org and repository have different scores?
Why do my org and repository have different scores?
Gabriele Gallo Stampino avatar
Written by Gabriele Gallo Stampino
Updated over a year ago

Variations on the following metrics:

  • Clayton Score

  • Technical Debt estimation

  • Benchmark

  • Remediation Effort estimated

  • Outstanding issues

may occur when the code under version control does not match the components deployed in the org.

This is often caused by one of these factors:

  • The org and the git branch you scanned are not aligned (i.e. the code deployed is either behind or ahead compared to what’s in the repo)

  • The org contains configurations or customisations that are not tracked under source control

  • The code under source control contains additional code or components that are not deployed to your org (e.g. additional scripting or packages)

  • The current org configuration in Clayton is not fetching certain metadata elements

Got questions? Don't hesitate to contact support, we here to help!

Did this answer your question?