Essentially these "phantom" connections are still "up" but aren't actually routing traffic anywhere, and Tandem’s connection process spends valuable time trying to verify these "dead" tunnels, which leads to:

• Long connection times
• Broken audio/video
• Frequent "reconnecting" messages

You can find immediate troubleshooting steps here: View Troubleshooting Guide

We’ve identified a specific technical conflict between Tandem’s connection protocol and certain VPN clients, specifically Mullvad, when they are installed on desktop machines and not necessarily in use. Here is a breakdown of what’s happening and how to fix it.

The Technical "Why"

Tandem relies on WebRTC (Web Real-Time Communication) to power high-quality video and audio. To make sure your call is as fast as possible, WebRTC uses a process called ICE (Interactive Connectivity Establishment) negotiation.

During this phase, Tandem:

1. Scans your machine for every available network interface.
2. Gathers "candidates" (potential connection paths).
3. Probes them with STUN/TURN requests to find the most efficient route to your teammates.

The Problem: "Phantom" Tunnels

When certain VPNs—like Mullvad—are installed, they sometimes enter a "half-state." Even if you have clicked "Disconnect," the VPN may leave behind multiple active tunnel interfaces.

Because these tunnels are still "up" but aren't actually routing traffic anywhere, Tandem’s connection process gets stuck. It spends valuable time trying to verify these "dead" tunnels, which leads to:

• Long connection times
• Broken audio/video
• Frequent "reconnecting" messages

The Solution

If you are seeing these issues and have a VPN installed, we recommend the following steps:

1. Fully Quit/Disable the VPN: Ensure no background processes are running.
2. The Clean Test: If the issue persists, try uninstalling the VPN temporarily and restarting Tandem.
3. Report Back: If removing the VPN solves your connection issues, please reach out to our support team.

Note on Mullvad: We have actively investigated Mullvad and confirmed that these phantom interfaces are a primary cause of failure. We are currently in contact with their team to find a more permanent compatibility fix.

We want your Tandem experience to be seamless. If you're still hitting walls after trying the above, let us know so we can dig deeper into your specific setup!

• Fixed an issue where some users experienced camera error "Camera access error. Try different camera or check if it is in use".

• Fixed microphone switching issues during calls.
• Fixed camera switching issues during calls.
• Call sub-windows no longer close automatically and now remain open while the cursor is over the window.

1. Updated Tooltip Text for Horizontal & Vertical Layout Toggle

2. Backend Logging Optimization

• We have implemented “TURN first” as a Team Settings parameter, visible to Team Admins.  When enabled, Tandem will bypass direct networks (which could be causing variable latency for highly distributed teams) and go via our TURN network.  This should improve call quality.

• Updated connection timeouts to improve overall call stability
• Improved connection-related logs with clearer prefixes and retry counters so debugging is easier and cleaner

• Add additional logs to help debug connection issues reported by some Tandem users.

• Fixed connection issue where it can sometimes take longer to reconnect.

• Fixed connection issue where it can sometimes take longer to reconnect.
• Implemented a fallback logic that is quicker to reconnect.

1. New User Signup: Resolved a bug in the signup flow.

1. Admin approval required for new accounts: Any new non-corporate user must now receive permission from Tandem Admin to register an account.
2. Control over automatic updates: Team admins can now disable automatic product updates for their team through a new setting.
   1. Go to Settings
   2. Open Team Settings
   3. Enable the "Disable auto update" option.

1. Resolved an issue where the 'Re-authorize' message was appearing for users who do not use Google Calendar.
2. Fixed a bug where connecting a calendar from a domain different than the registered email domain showed a success message, despite the mismatch. Now, an error message will be displayed when the domains do not match.

1. Google Calendar Sync –  Fixed issue where there is a false message to re-authorize with Google to sync messages.