“Meeting code has expired”

The “Meeting code has expired” error in Google Meet occurs when you try to join a call using a meeting token whose server-side lifespan has ended. Every Google Meet URL contains a unique 10-letter code (abc-defg-hij) governed by specific expiration rules depending on how the meeting was created. Once a meeting code reaches its expiration threshold or a temporary room closes, Google’s lookup table purges the token, blocking any further attempts to connect.

Fast-Fix: The 45-Second Solution

The “Meeting code has expired” error occurs when a Google Meet link exceeds its lifespan or when accessing a closed nicknamed meeting room. To fix this, ask the host for an updated invitation link or generate a new meeting directly from meet.google.com or Google Calendar. Risk: Low (Access failure only).

Quick Risk Snapshot

• Severity: Low (Prevents call entry; does not impact account data or security)
• Safe to Join?: N/A (Access is completely blocked by the server)
• Primary Cause: Attempting to reuse an old calendar link, instant meeting code, or closed nicknamed room
• Rare Cause: Host account deletion or Google Calendar event sync failure

Low Risk vs. High Risk Paths

• Low-Risk Path (Expired One-Time or Nicknamed Link): The meeting code was generated for a previous one-off session, a nicknamed room that closed after all participants left, or an old Calendar invite whose token expired. Generating a new link resolves the issue immediately without affecting underlying account settings.
• High-Risk Path (Recurring Event Synchronization Failure): The error consistently appears across an active recurring calendar series for all domain users. This points to a broken integration between Google Calendar and the Meet service token database, requiring the host to recreate the recurring event or clear stale calendar attachments.

How Google Meet Codes Expire

Think of a Google Meet code as a digital security badge programmed with a specific shelf life. Depending on how the badge was issued, the access lock resets on different schedules:

• Google Calendar Links: Codes generated through scheduled calendar events remain active for the duration of the scheduled event and stay valid for up to 365 days after their last recorded use, provided the event remains on the host’s calendar.
• Instant Meetings: Codes generated by clicking “Start an instant meeting” on meet.google.com expire exactly 365 days after their last active use.
• Nicknamed Meetings: Available to Google Workspace subscribers, nicknamed links act like temporary disposable locks. The moment the last participant exits a nicknamed call, the meeting code expires instantly and cannot be reused by anyone.

When you enter an expired code, Google Meet queries its active meeting index. Finding no matching active session, it rejects the connection attempt before initiating audio or video handshakes.

Probability Breakdown

• Reusing an Old or Stale Meeting Link (55%): Attempting to join a meeting using a bookmarked URL or an old email link from a call that concluded days or weeks prior.
• Closed Nicknamed Meeting Room (25%): Trying to rejoin a Workspace nicknamed meeting after all attendees, including the host, have disconnected.
• Deleted or Updated Calendar Event (15%): The meeting organizer modified, canceled, or re-created the event, which assigned a brand-new meeting code while leaving the old link behind in local notes.
• Workspace Account or Domain Policy Shift (5%): The account that originally created the meeting code was suspended, deleted, or transferred to an organizational unit with restricted calling permissions.

What Increases the Risk

• Bookmarking direct meeting URLs in browser toolbars instead of launching calls from live Google Calendar events.
• Using Workspace meeting nicknames for recurring team check-ins rather than establishing a permanent recurring Google Calendar entry.
• Copying meeting links manually into third-party documents or messaging apps where link updates are not synced automatically.
• Keeping calendar entries open across multiple third-party client applications that fail to push meeting token updates correctly.

Consequence Timeline

• Immediate: Google Meet displays the “Meeting code has expired” warning card upon entering the URL, preventing access to the greenroom or pre-join screen.
• 5 Minutes: Attendees manual-reload or attempt to re-type the 10-letter code, leading to delayed meeting start times.
• 15 Minutes+: Continued reliance on the expired token forces the organizer to set up a replacement room and redistribute the new link across all meeting participants.

What This Is Confused With

• Expired Code vs. Invalid Link: An expired code means Google’s servers recognize the token format, but its active life cycle has ended. An invalid link error means the URL contains structural typos, missing hyphens, or corrupted characters. For formatting and syntax failures, see “Meeting link is invalid” (Recurring Events).
• Expired Code vs. Permission Block: Expired code errors stop you before entering the room setup screen. Permission errors occur when the room is active, but your account lacks access privileges or the host has not let you in. For permission failures, see “You are not allowed to join this meeting”.

What To Do Right Now

• Join Directly from Google Calendar: Open Google Calendar, locate the active event entry for the current time slot, and click the blue “Join with Google Meet” button to ensure you are pulling the current token.
• Request an Updated Invite: Ask the meeting host or organizer to open the event card, verify the current Meet link, and send a fresh invitation or chat message with the active URL.
• Spin Up an Instant Replacement Room: If you are the host, navigate to meet.google.com, select New meeting > Start an instant meeting, and copy the new joining info to distribute to your team.
• Verify Account Switching: Ensure your browser is using the correct Google profile. Switch to the organizational account that received the original calendar invite if you are currently signed into a personal Google profile.

Hard-Stop Triggers

Stop standard troubleshooting and contact your system administrator or host under the following conditions:

• The account that created the meeting invite has been deactivated or deleted by your organization.
• Your Google Workspace administrator has restricted video call creation privileges for your account level.
• The host confirmed the calendar event is active, but every user in the domain receives the same expiration error when clicking the event link.

What an Admin Will Check

When escalated to an IT administrator or Google Workspace manager, technical staff will investigate the following areas:

1. Google Workspace Audit Logs: Reviewing the Meet audit logs inside the Admin Console (Reporting > Audit and investigation > Meet log events) to verify the exact time the meeting code was deactivated or closed.
2. Calendar Integration Headers: Checking if third-party scheduling tools or sync plugins stripped or overwritten the conferenceData object attached to the calendar event.
3. Organizational Unit (OU) Video Calling Rules: Verifying that the host’s account retains active rights to host video calls under Apps > Google Workspace > Google Meet.

Typical Effort Range

• Minor (1–2 Minutes): Requesting a fresh meeting link from the host or clicking the active link directly inside Google Calendar.
• Moderate (5–10 Minutes): Clearing a broken recurring event series and issuing a fresh meeting invitation to all scheduled participants.

Related System Escalators

• If your meeting link fails due to a generic server-side joining failure, see “Something went wrong” (Error 500) Joining Meet.
• If participants cannot see the option to knock or request entry after joining a new room, see “Ask to join” button missing for invited guests.
• If Google Calendar fails to display or generate video links properly, see “Calendar could not be loaded” (Internal Error).
• If you encounter broken links on automated booking pages, see Troubleshooting “Appointment Schedule link 404”.

Workspace Assessment

The “Meeting code has expired” error is simply a token lifecycle boundary enforced by Google’s meeting servers. Obtaining a fresh link directly from an active Google Calendar event or creating a new instant meeting room will bypass the stale code and restore your video connection immediately.