FireHydrant: Zoom scribe unable to join calls
Affected components: Zoom
Timeline of updates
- monitoring
Our Zoom scribe is currently unable to join meetings. We are actively investigating this issue and will post updates to the status page.
Incidents and Zoom meetings themselves are operating normally.
- monitoring
We have identified the issue with Zoom transcriptions and are working toward a solution.
As an alternative, Google Meet transcriptions continue to work as expected.
- monitoring
We have identified the issue with Zoom transcriptions and are continuing working toward a solution.
As an alternative, Google Meet transcriptions continue to work as expected.
- monitoring
We have been in active contact with Zoom support and are actively working on resolving the issue. We will continue to provide updates here as we get them.
As an alternative, Google Meet transcriptions continue to work as expected.
- monitoring
Recommendation for AI Transcription Functionality
As our team is actively working to resolve an incident impacting Zoom-based transcription, Zoom bridges are still being created successfully and you can continue to use Zoom for incident calls. However, FireHydrant's AI transcription feature is unavailable within Zoom. While we work directly with Zoom to resolve the issue, we recommend temporarily switching to the Google Calendar integration to ensure your incident calls continue to be transcribed without interruption.
What this means for you
AI transcription on incident calls will not function reliably when using the Zoom integration.
Connecting the Google Calendar integration allows FireHydrant to continue capturing and transcribing incident calls as expected.Steps you can take
Enable the Google Calendar integration in your FireHydrant workspace.
Add a runbook step that creates a Google Calendar Event and select "Yes" when asked "Transcribe Meeting?" so FireHydrant can capture and transcribe the incident call.This is a temporary workaround to allow FireHydrant to continue detecting, recording, and transcribing incident meetings while we actively work with Zoom on a fix. We’ll keep you updated as soon as the issue is resolved and the Zoom integration is fully operational again.
If you need help enabling the Google Calendar integration, please reach out to your CSM or our support team.
Thank you for your patience while we work through this.
- monitoring
We have received an update from Zoom support and are testing the changes now. We appreciate your patience in this matter
- monitoring
We have partially restored Zoom scribe functionality for meetings without waiting rooms or where the host is present to admit the bot from the waiting room.
The bot will join as a "Meeting scribe" and will need to be let into the meeting room by the host. Please disable waiting rooms if possible to continue functionality.
We will continue to update as we work to resolve this issue.
- identified
During the migration of the zoom marketplace application, credentials were invalidated. This is leading to authorization errors when creating zoom bridges on FireHydrant. We are investigating the issue and expect to have this remediated shortly.
- monitoring
Zoom credentials have been successfully updated. Reauthorizing failing zoom connections will now work as expected.
- resolved
We are testing new Zoom scribe settings and are working on confirming the fix
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.firehydrant.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by FireHydrant, started 2026-03-02 23:30 UTC, resolved after 3 d, 10 update(s).
- Title
- Zoom scribe unable to join calls
- Vendor
- FireHydrant
- Date
- URL
- https://rewindex.com/company/firehydrant/incidents/1f6ce8b2-2961-41f8-af66-723d0a3c2dc9
FireHydrant profileRecent FireHydrant incidentsAll outages on March 2, 2026FireHydrant in March 2026MarkdownJSON