When we try deploy a workflow in prod mode that has persistence configured, like  https://github.com/flows-examples/techpreview2#use-case-3-persistence
 
We have the following situation.
 
The workflow can be deployed, etc, but if we look in the respective POD logs we can see this message:
 
 
2023-09-12 07:09:13,949 WARN [io.qua.run.con.ConfigRecorder] (main) Build time property cannot be changed at runtime:

• quarkus.flyway.locations is set to 'classpath:/db/postgresql,db/migration' but it is build time fixed to 'db/migration'. Did you change the property quarkus.flyway.locations after building the application?
• quarkus.devservices.enabled is set to 'false' but it is build time fixed to 'true'. Did you change the property quarkus.devservices.enabled after building the application?
  2023-09-12 07:09:13,954 DEBUG [io.ver.cor.log.LoggerFactory] (main) Using io.vertx.core.logging.SLF4JLogDelegateFactory
   
   
  So, the flyway path that is being picked up is "db/migration", but the xxx.sql files are not there. Looking at the message, we can see that this property was already build time fixed.
   
  As soon we try to create  workflow instance we get an exception because the process-instances table was not created.