# 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:** 9

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [January 8, 2024, 8:27pm UTC](https://meta.discourse.org/t/tracking-and-resolving-a-schema-drift-cause/290901/9 "2024-01-08T20:27:21Z")

</div>

> [@jrack](#):
>
> 20231022224833

We happen to have a database with all migration ID’s for 400+ plugins so we can map them to a plugin easily. This one comes from discourse-automation.

---

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