Skip to content

Why does TranscripTonic sometimes experience a sudden downtime?

Vivek G edited this page Sep 9, 2025 · 1 revision

A little about how TranscripTonic works with Google Meet UI

TranscripTonic closely depends on the Google Meet UI for various functions. When Google makes updates to the Google Meet UI, TranscripTonic will not automatically know how to work with the new UI and has to be updated.

Example: When you click the end call button, TranscripTonic will consider that meeting has ended. The end call button is identified by certain parameters like id, class, button text etc. When Google changes this in an UI update, TranscripTonic will not be able to automatically handle it and needs to be updated to work with the changes done by Google.


Can the downtime be predicted and fixed in advance?

As explained above, it is the meeting UI changes that cause downtimes. There is no way to know in advance, if the meeting UI will be updated. So, unfortunately there is no way to predict and fix in advance.


Why does it take days for the fix to be available?

Usually, once I know there is an UI update that is causing problems, I try and come up with a fix very quickly. However, since the extension is made available on Chrome Store, every change has to go through their review. Chrome Store review does not accept any exceptions to fast track urgent fixes. Their review times can take a few days to a week and there is nothing that can be done, but to wait for their review and approval.

To overcome this, I provide unpacked version of the updated extension that can be directly installed, while the review is in progress.


If you have any questions, please create an issue here.

Clone this wiki locally