Liquibase BeanCreationException - change log referred is not visible in studio

I have a FlowUI application that recently got strange exceptions.

When I generate the database changelog, liquibase generates it and when executes, got the following exception.

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jmix_Liquibase' defined in class path resource [io/jmix/autoconfigure/data/JmixLiquibaseAutoConfiguration.class]: Invocation of init method failed; nested exception is liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for change set com/inteacc/main/liquibase/changelog/2023/01/01-010957-34c1de62.xml::1::main:
     Reason: liquibase.exception.DatabaseException: There is already an object named 'MD_CUSTOMER_CONTACT' in the database. [Failed SQL: (2714) CREATE TABLE MD_CUSTOMER_CONTACT (ID uniqueidentifier NOT NULL, VERSION int NOT NULL, FIRST_NAME varchar(255), LAST_NAME varchar(255), TITLE varchar(255), PHONE varchar(255), EMAIL varchar(255), MOBILE varchar(255), CONSTRAINT PK_MD_CUSTOMER_CONTACT PRIMARY KEY (ID))]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1804) ~[spring-beans-5.3.24.jar:5.3.24]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:620) ~[spring-beans-5.3.24.jar:5.3.24]

As you see it is referring to the change log file 01-010957-34c1de62.xml however, my studio datastore folder does only a different change log file. I searched for that file and tried to fix it by inactivating the script as the table is already existing but it doesn’t work, giving null exceptions.

image

How can I resolve this, any suggestions?

Hi

Are there any add-ons used in the project? If so, please check these add-ons for the presence of the com/inteacc/main/liquibase/changelog/2023/01/01-010957-34c1de62.xml changelog file.

Yes I have that file and that code is causing such issues because the code was executed already earlier and for some reason, it is trying again to execute.