# Using cassandra migration in new custom plugin dosent work

**URL:** <https://discuss.konghq.com/t/using-cassandra-migration-in-new-custom-plugin-dosent-work/685>\
**Category:** Questions\
**Created:** [March 14, 2018, 8:32am UTC](https://discuss.konghq.com/t/using-cassandra-migration-in-new-custom-plugin-dosent-work/685 "2018-03-14T08:32:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lorin\_Totah](https://avatars.discourse-cdn.com/v4/letter/l/94ad74/32.png) [@Lorin\_Totah](https://discuss.konghq.com/u/Lorin_Totah)\
**Post date:** [March 14, 2018, 8:32am UTC](https://discuss.konghq.com/t/using-cassandra-migration-in-new-custom-plugin-dosent-work/685/1 "2018-03-14T08:32:40Z")

</div>

I start implementing new custom plugin using Cassandra migration script. I’m using Kong 0.11.2,  
When running `kong migration up` command Kong notify that migration is up to date. (The custom plugin tables were not created.)  
However, when I go to start Kong again, I get this error:

`the current database schema does not match this version of Kong. Please run`kong migrations up`to update/initialize the database schema. Be aware that Kong migrations should only run from a single node, and that nodes running migrations concurrently will conflict with each other and might corrupt your database schema!`

When I’m running kong migration reset && kong migration up, It works, I cant run it in production but it seems when I run it locally that it doesn’t really reset anything and it works.

Any ideas on what I can do or might be doing wrong?