MSSQL backend does not use correct task hub

When using durable functions monitor with the MSSQL backend in the default multi-tenant configuration, the monitor seems to discover the task hubs correctly, but does not use them when querying instances.

I have a SQL server deployment with 3 task hubs, the task hubs are correctly identified:

Regardless of which task hub is selected, the dbo task hub contents is shown in the list

DBO

DIO

Nicktest

I can see the data is available by querying the table directly.

If I try and navigate to an instance directly using the id from the database, I get a not found error.

I'm using the docker container to run functions monitor with this command:

docker run --rm -p 8072:80 \
    -e DFM_SQL_CONNECTION_STRING='<REDACTED>' \
    -e DFM_NONCE="i_sure_know_what_i_am_doing" \
    scaletone/durablefunctionsmonitor.mssql:6.6

Start with the MSSQL backend using the supplied Docker command and the default multi-tenant configuration, then compare the selected task hub with the SQL table contents. Reproduce the list and direct-instance queries for DBO, DIO, and Nicktest; done means each selected hub shows its own instances and direct navigation finds an instance from that hub.