While developing we had the following issue:
We changed the termtagger URL in the DB config, but on the next run the old URL was used.
The problem is complex:

• One part is the problem that the configured URL is directly used as worker slot, which is not nice but possible and simplifies the handling with slots and URLs.
  The question is now: why does a new Worker started after the config was changed, tries to use the old config values? Does he use the wrong slot content? Was it the old worker who was reactivated?

Please check and fix.