# Tracking and resolving a schema drift cause

**URL:** <https://meta.discourse.org/t/tracking-and-resolving-a-schema-drift-cause/290901>\
**Category:** Self-hosting\
**Created:** [January 8, 2024, 7:02pm UTC](https://meta.discourse.org/t/tracking-and-resolving-a-schema-drift-cause/290901 "2024-01-08T19:02:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)\
**Post date:** [January 8, 2024, 7:14pm UTC](https://meta.discourse.org/t/tracking-and-resolving-a-schema-drift-cause/290901/2 "2024-01-08T19:14:06Z")

</div>

> [@jrack](#):
>
> Both sites are at app 3.1.3

Could it be the old one was on beta or tests passed and not stable, so the latest stable is in fact, older?

I’d check the commit numbers match (if possible).

The backup is of the db, so I doubt plugin population matters, it will simply add the plugin data but not actually use it …

---

_[View the full topic](https://meta.discourse.org/t/tracking-and-resolving-a-schema-drift-cause/290901)._