Church wifi blinks, a phone locks in a pocket, the laptop at the sound desk loses its connection for a moment. Since 29 September 2026, MulingStream reconnects by itself and the translation carries on, for the speaker and for every listener, without anyone pressing a button.
Every church that has run live translation knows the moment. The sermon is going well, the guests are following on their phones, and then the wifi in the building blinks. Or the laptop at the sound desk drops its connection for ten seconds because somebody plugged in a kettle on the same circuit. Or a listener's phone locks in a pocket and wakes up again.
A connection that drops for a moment is ordinary. What matters is what happens next. Until this autumn, a short drop could mean a volunteer had to notice, stop the stream, sign in again and start over, while the people listening heard nothing and wondered whether it had broken for good. On a Sunday morning, with the service carrying on at the front, nobody has time for that.
So we changed it. Since 29 September 2026, MulingStream reconnects by itself, on the speaker's side and on the listener's side, and the translation carries on where it left off.
In an office meeting, a dropped call is a small annoyance: everybody waits, somebody says "you froze", and you carry on. A service does not wait. The pastor keeps preaching, the worship team keeps playing, and the person who depends on translation is the one person in the room who cannot follow what is happening while it is gone.
That person is also the least likely to say anything. A guest who suddenly hears silence in their earbuds does not walk up to the sound desk in the middle of the sermon. They assume it has stopped, put the phone away, and sit through the rest without understanding. The church never finds out. That is why we treat reliability as part of the translation, not as a technical detail behind it.
A service does not wait for the wifi. So the translation has to find its own way back.
The speaker's device is the one that matters most, because everything starts there. Here is what MulingStream does now when that connection drops during a live session:
A short drop is bridged by itself. When the connection comes back, the session continues in the same room, with the same languages, and the listeners carry on. Nobody has to press start again.
A longer interruption resumes itself too. If the page had to reload, or the browser was closed by accident, MulingStream recognises the session you were running. A short message says the stream was interrupted, counts down ten seconds, and resumes the session on its own. If you would rather start fresh, you can discard it instead.
The stream survives an expired sign-in. If your sign-in runs out in the middle of a service, the stream keeps running. A quiet note tells you to sign in again in a new tab when you have a moment, and nothing stops while you do.
The screen stays awake. A laptop or tablet that goes to sleep during a long sermon used to take the stream with it. MulingStream now keeps the speaking device awake while you are live, and tells you if the device refuses.
Remember me. Tick Remember me when you sign in, and that device stays signed in, so Sunday morning starts without hunting for a password.
Listeners have their own drops: the phone locks, they walk out to the foyer with a child, the mobile signal fades at the back of the hall. Those are now handled the same way.
If a listener's connection is interrupted, their screen says so and shows that it is reconnecting. When the connection returns, they are back in the room, in the language they chose, with the audio and the text running again. They do not have to scan the code a second time or find their language in the list again.
A phone that locks with the audio on keeps the listener in the room, rather than counting them as gone, and when they come back to the page they come back to the language they left on. If the phone itself has paused the sound, as some phones do after a while, a single tap on Resume brings the translation back. Read more about the guest's side on how it works for listeners.
Churches that show the translation on a screen with MulingDisplay get the same behaviour. If the display loses its connection, it says so and reconnects automatically, so nobody has to go up to the projector laptop in the middle of the service.
This did not arrive in one step. In May 2026 we made sure a speaker could always take back their own room after a drop, with a clear Resume Live button and a visible notice when the connection was lost, instead of a room that stayed locked. Through September we watched real Sunday services closely, found every place where a short drop still turned into a long silence, and fixed them one by one: the session now holds on through a drop, a reload resumes itself, and an expired sign-in no longer stops anything. The last of that work reached MulingStream on 29 September 2026.
We did it this way because churches told us, plainly, that a translation that stops is worse than none. A guest who loses the sermon halfway through feels more left out than one who never had it. So the goal is simple: once you press start, the translation keeps going until you press stop.
Reconnecting by itself does not make a weak connection strong. A few simple habits make every Sunday smoother:
Put the speaking device on the most reliable connection in the building. A cable to the router, or a phone hotspot kept ready as a backup, is worth more than any setting.
Run the Microphone check in your room settings once, so we know your normal speaking level and can warn you when something sounds wrong.
Keep an eye on the Mic level and Clarity meters while you are live. They show at a glance whether we are hearing you clearly.
You can read more about the sound side of a service on sound and media, and about everything else that changed this autumn in our release notes for July to October 2026.
We show you the whole thing live, in about fifteen minutes. Nothing is decided on the call and nothing follows it: you see it, and then you are the judge.