The Designer front-end tool caches certain data in a local SQLLite database.
Are there any potential problems with parallel changes made via Designer when two or more instances are running and connected to the same database?
If two instances of Designer are being run in parallel, changes applied to the database by one Designer instance may go unnoticed by the other until it reloads data or is restarted.
The same is true for manually applying changes to the database, e.g. configuration parameters, while a Designer instance is running at the same time. Keeping this possibility in mind before applying changes to the database is a good idea.