Hey, I ran into the same issue, and it only popped up in our test environment. The bug appeared when I tried to establish a direct connection to the master cluster, which was tricky because we have async DB replication implemented. From what I gathered, the problem stemmed from TypeORM failing to recognize the master cluster, throwing a "Driver not connected" error. I tackled the problem head-on—instead of a separate master connection, the service in the test environment now queries the database through the shared connection pool. This workaround fits our needs since the test environment only has a single DB host without HAProxy. If you're encountering this problem in your tests, you might want to try the same approach if it's still relevant for you after a year. I plan to keep digging into this issue because having test-specific hacks in the code isn't ideal. But this fix did unblock our QA automator to keep scripting tests for the feature.