Your recurring meeting moved—and its Google Meet link changed

You moved your weekly meeting to a new time, and the invitation now shows a different Meet link. Is it safe to paste the old link back in?

Your recurring meeting moved—and its Google Meet link changed
TLDR
  • When you move a regular meeting to a new time or repeat schedule from a chosen date, participants may need a new joining link too. Calendar generates it when you change the start time or recurrence for “This and following events”; the earlier series keeps its original link.
  • Reopen the first changed occurrence and distribute its current joining information. Update links copied into notices and bookmarks as well.
  • Reusing an old code can leave new guests asking for admission while the original guests retain access to recordings or notes. The code still belongs to its original event. Create a new one if you cannot identify that event.

If moving a recurring meeting also changes its Meet address, open the first updated occurrence and use that event’s joining information. Pasting the familiar address back can leave newly invited guests waiting for admission, while people from the original event retain access to recordings or notes. A Calendar-generated code stays associated with its first event until it expires; editing a different invitation’s guest list does not replace that association.

A URL typed into a team notice or a reusable email template stays there when you change the Calendar event. Replace it with the updated occurrence’s address so guests following the notice reach the same call. If people have joined or left the group, check the revised invitation’s guest list as well.

Which edits generate a new Meet link?

Google announced this behavior on November 19, 2025. When you change a recurring event’s start time or recurrence and apply it to This and following events, the remaining events receive a new Meet link. The original series retains its link. This applies to personal Google Accounts and all Workspace customers, with no separate user or administrator setting to disable it. Recurring-event link changes

The conference’s properties, including hosts, co-hosts, access restrictions and recording, are preserved for both links. A new address does not mean you must rebuild all host settings. It also does not mean that recordings from previous occurrences have been copied into the new events.

Compare the last occurrence before the change with the first one afterward. Their titles may match while their joining addresses differ. Check the start time, repeat rule and selected edit scope when tracing what changed.

Move the meetings from the intended date

Suppose a weekly Tuesday meeting will move from 2 p.m. to 3 p.m. starting next week. You want previous meetings left as they were. Begin with the first occurrence that should use the new time, rather than opening an arbitrary past occurrence.

  1. In Google Calendar on a computer, open the relevant occurrence and select Edit. Check the organizer and date if several meetings have similar names.
  2. Change the start time and check that the end time still gives the intended duration. Adjust the repeat rule if the frequency is also changing.
  3. Save, then select This and following events for this example.
  4. Reopen the saved occurrence and inspect its time and Meet address. Check the following occurrence too.
  5. Open the occurrence immediately before the change to confirm that the earlier schedule remains as intended. Take the new joining address from the updated event.

Calendar’s help describes the edit, save and occurrence-selection sequence. Choose the scope according to the scheduling change you actually need. Editing a repeating event

Intended changeScopeOccurrences to compare
Move one meeting onlyThis occurrenceThe changed date and the next meeting
Move meetings from a date onwardThis and following eventsThe preceding, first changed and next occurrences
Revise the entire seriesAll eventsRepresentative past and future occurrences

Do not choose a broader scope solely to try to retain a familiar URL. If you only intend to change future meetings, preserve that boundary and communicate the resulting address. If some dates were previously rescheduled individually, open those exceptions too before announcing the revised schedule.

An old code can retain an old guest list

You can paste an existing code into another invitation, but a Calendar-generated code remains linked to its original event until it expires. A new invitation does not automatically replace that association. Google’s March 2026 update made this relationship explicit. How Meet calls connect to Calendar events

Newly invited people may need admission from the host, while records such as recordings or notes can remain accessible to the original event’s guests. When continuous meeting chat is enabled, people from the original event may receive messages from the new meeting. Being able to open the call therefore does not establish that its records follow the new invitation’s guest list. Meeting-code permissions

Consider a project call with an external partner followed by a separate internal review. Leaving the partner off the internal invitation does not make the project call’s reused code an internal-only code. Create the internal review as its own event with its own Meet conference.

This manual reuse is different from Calendar generating a fresh link when you split a recurring schedule. In the latter case, distribute the updated event’s address. With a pasted code, you also need to understand the event and guest permissions behind it.

Update the invitation and the places people actually click

Send the event update when Calendar offers to email guests. Google recommends these emails to make changes visible. A guest who has turned off email notifications or automatic invitation additions may miss the update. Ask them to check for the invitation email and the revised occurrence on their calendar. Event invitations and updates

If an external participant cannot find the invitation, ask them to check the invitation email and respond Yes or Maybe. Unfamiliar senders and settings that prevent automatic event addition can require that response. Other calendar services also handle the update according to their own settings.

A short notice should identify the first affected date, the new time and where to join. For the hypothetical Tuesday meeting, you could write:

“Starting next Tuesday, this meeting moves to 3 p.m. The Meet link has changed too. Please join from the updated Calendar invitation and replace any bookmark with the link shown there.”

Use an explicit date and time zone in the real message. Then check the pinned team notice, meeting instructions and reusable email text. Simply appending another URL leaves participants to choose between two plausible addresses. Keep the current joining information prominent; label historical links as belonging to past occurrences if you need to retain them.

If somebody reports that they are in an empty call, compare both the occurrence date and the meeting code. The organizer should point them to the updated invitation for that date. This is particularly useful when a current invitation and an old bookmarked address coexist.

Replace a code linked to an unfamiliar meeting

Calendar may warn that a code comes from a different meeting. If you cannot identify that original event, generate a new code. The desktop procedure removes the conference, saves the event, and then adds a new Meet conference after reopening it. Resolving a meeting-code warning

  1. Edit the event and remove the existing conference using the control next to it.
  2. Save. For a recurring event, check the intended scope of the change.
  3. Reopen the saved event, select Edit, and choose Add Google Meet video conferencing.
  4. Save again, inspect the new joining information and guest list, and distribute the necessary update.

You need permission to edit the event. A participant without that permission should ask the organizer or an authorized editor to change it. Deleting a URL typed into the description is not the same action as removing the conference from its dedicated field. Adding and removing event conferences

Inspect the location and description afterward. An old URL entered manually, another provider’s address or text inserted by an extension can remain alongside the current conference. Make the intended joining route clear before distributing the invitation again.

A working old link is not the next meeting’s address

A newly generated link does not establish that the previous code expired immediately. The current Meet help, checked October 27, 2026, says a Calendar-generated code expires when it has gone unused for 60 days and has no future Calendar events associated with it. Codes created through Gmail or the Meet homepage instead expire 365 days after their last use. Meeting-code expiration rules

Pasting a code from another product into Calendar does not change the product that generated it. Its original expiration rule still applies. Whether a URL opens and whether it is the correct address for the next occurrence are separate questions.

Creating Google Calendar events with Meet through Apple Calendar or another calendar app can also produce a replacement code and an email notification. If several apps were involved, inspect the occurrence in Google Calendar on the web or in its app rather than repeatedly restoring an older address.

For the first meeting after the change, the organizer and guests should use the same dated invitation. Keep its time, guest list and conference address together as the reference. That makes an outdated notice easier to identify before people arrive in separate calls.