Errors on upgrade from 2.37 to 2.40?

[Gassim (AL-Gassim Sharaf Addin)]

Hi @doodoocoder

Thank you for your suggestions.

@doodoocoder

flyway_schema_history

I don’t think this is a recommended approach. Please read the following [note](https://community.dhis2.org/t/flyway-error-in-2-33-3-snapshot-on-using-2-32-database-on-second-startup-the-server-started-fine-on-first-attempt/38772/3:

@Ameen

Dear all

Please do not delete the flyway table. That is not a solution.
The flyway schema history table is internal and its needed by flyway to track the changes of the schema and verify consistency of the database.
Every error that flyway throws will have a reason, and its important to find the reason rather then trying to delete the table and lose precious info on why flyway threw an error in the first place. Its more likely to end up in an inconsistent state and all future flyway migrations will have issues if you delete or modify the flyway_schema_history table without understanding the root cause of the issue.

In short, please do not delete flyway table ever

@linxd, I would recommend to test @Ulanbek’s suggestion please and see if it clears aways the scheduler issues?

Thanks!