Unfortunately there was a regression introduced in 8.1.20 that can affect query tags that target the same database connection across different tag providers. There is a fix coming soon in 8.1.21 to mitigate this (it is not in the current RC, though). At the moment, a workaround is to define a duplicate database connection (with a different name) and use that to keep query tags on a given provider targeting their own database connection.