A Google Calendar invite is not showing up: where it stopped

Someone says the meeting is booked. The grid on the Mac says nothing is there. Before touching the account, it helps to know that a Google Calendar invite not showing up is almost never lost mail and almost never a broken sync. In most cases the invite arrived, was evaluated against one specific setting, and was held back on purpose. The useful question is not "where did it go" but "which gate stopped it", because each gate has a different fix and only one of them is worth changing permanently.

The invite did not vanish. It stopped at one of four gates

An invitation has to clear four checks before it becomes a block of colour on the screen. Working through them in order saves a lot of guessing.

The first gate is the address. An invite sent to an alias, a forwarding address, or an old work account never reaches the calendar that is open on the Mac, because a calendar only shows events addressed to the account that owns it. This is worth ruling out first because it costs nothing: open the invitation email and read the address in the To field rather than the one in the mail client's title bar. A single character of difference, or a domain that was migrated two years ago, explains the whole thing.

The second gate is the sender policy. Google Calendar evaluates who sent the invite and decides whether to write it into the grid automatically or leave it sitting in email. This is the gate that catches most cases, and it is the one described in the next section.

The third gate is the recipient shape. An invite sent to a Google Group behaves differently from an invite sent to a person, even when the group delivers to the same inbox.

The fourth gate is the client. Google Calendar on the web can be holding the event while the calendar app on the desktop has not pulled it yet, which looks identical to the event not existing.

Those four are not equally likely. Sender policy accounts for the bulk of reports, the address mismatch for most of the rest. The client is last for a reason: it is the gate people check first and the one that is least often responsible.

There is also a category that never reaches any of the gates. Plenty of meetings are not sent as invitations at all. A time agreed in a chat thread, a schedule pasted into the body of an email, or a booking confirmation written as prose carries no structured event for a calendar to act on. Nothing is missing in that case, because nothing was ever sent in a form a calendar can read. Recognising this early avoids an hour of settings work on a problem that settings cannot touch.

The setting that decides whether an invite lands

The control sits in Google Calendar on the web, at Settings, then General, then Event settings, under the label Add invitations to my calendar. It has three values, and Google's own documentation on managing invitations in Calendar spells out what each one does.

From everyone writes every invitation into the calendar automatically. The documentation adds an important limit: this applies to invitations sent directly to the email address on the account. An invite that arrives through a Google Group is not covered.

Only if the sender is known writes the event automatically when the sender is in your contacts, is part of the same organisation, or is someone there has been previous interaction with. When the sender does not qualify, no event is created and an invitation email is sent instead. Once a sender is marked as known, or once there has been an interaction, later invitations from that sender go in automatically.

When I respond to the invitation in email creates nothing until the email itself is answered. This is the quietest option and the one most likely to look like a failure, because the sender sees an unanswered invite while the recipient sees an empty day.

One line in the documentation explains a large share of confused reports: updated settings only apply to new invitations. Changing the option does not go back and rescue the invite that is already missing. That one has to be handled by answering the email.

Which option to pick, and what each one costs

None of the three is correct in general. They trade spam exposure against the risk of a silent miss.

Setting	Events appear without action	Exposure to calendar spam	Failure mode to expect
From everyone	Always, for direct invites	Highest	Unwanted events land in the grid
Only if the sender is known	For contacts, colleagues, prior contacts	Moderate	First invite from a new client is missed
When I respond to the invitation in email	Never	Lowest	Any unread invitation email is a missing meeting

There is a second cost worth knowing about before choosing the middle option. The documentation warns that selecting Only if the sender is known might reveal to senders that they are not in your contacts, because the invite behaves differently for them. For sales work or recruiting, where the sender is often a stranger who matters, that signal is not free.

On a work or school account the choice may not be available at all. Administrators control which invitation settings can be used, so an option that is greyed out has been restricted for the organisation rather than broken.

When the invite was sent to a group, not to a person

This one is easy to misread as a bug because the strongest setting appears not to work. With From everyone selected, an invite that was addressed to a Google Group still does not appear automatically. Google documents the behaviour plainly: for invitations sent to a group you belong to, responding to the email is what adds the event to the calendar.

The practical effect shows up in teams that schedule to a shared address on purpose. Invites to a group land in every member's inbox and in nobody's calendar, which is exactly the situation where everyone assumes somebody else has it handled. If a recurring meeting is the kind that must never be missed, sending it to individual addresses rather than to the group removes the extra step for everyone at once.

For invitations that were forwarded from another address, there is a separate switch. Google's page on responding to event invitations describes an option under Other notifications that allows responding to invitations forwarded through alternative email addresses. Without it, answering a forwarded invite can fail silently.

Clearing the unknown sender state for good

When invitations from a sender keep getting marked as an unknown sender even after an exchange of mail, the cause is usually one level below Calendar. Google's documentation points at the Google Account setting that allows Google products to save contact information when you interact with people. With that turned off, no interaction ever promotes a sender to known, so the middle option behaves like the strictest one forever.

Two fixes follow from that. The reliable one is to add the sender to contacts manually, which the documentation recommends outright for connections whose invites must always land. The other is to check whether the sender was blocked somewhere else: a contact shows up as an unknown sender if they were blocked from another Google product, so the block travels into the calendar without any calendar setting explaining it.

The reverse case matters too. Marking a sender as known by mistake is undone at contacts.google.com, under Other contacts, by deleting the entry. Anyone running a calendar that receives spam invites will end up doing this occasionally.

On Android there is one more place to look. If spam events keep appearing even with the strict option selected, the documentation suggests reviewing which apps have access to the calendar, since a third party app with write access can create events without any invitation being involved.

When the grid on the Mac is the part that is behind

Once the invite is confirmed present in Google Calendar on the web, a missing event on the desktop is a refresh question rather than an invitation question. Apple's guide to refreshing calendars documents the controls: an account level Refresh Calendars menu under Calendar settings, a Push option that updates as soon as a change happens on any device using the same account, and View then Refresh Calendars for an immediate pull.

The interval is the detail that decides how this feels day to day. An account left on a timed refresh will show an invite that arrived ten minutes ago as nothing at all, which is indistinguishable from the invite never existing. For work where meetings get moved on the day, Push is the setting that stops the guessing, because the desktop stops being a delayed copy.

Subscribed calendars are separate again. They carry their own Auto refresh interval, reached by Control clicking the calendar and choosing Get Info, so a shared roster or a holiday feed can be stale while everything else is current.

One more detail catches people who connect a Google account to a desktop calendar and expect the two to be identical. A calendar client shows the calendars it was told to sync, and a calendar that was added on the web after the account was connected is often not among them. An invite written into that newer calendar exists on the account and is invisible on the desktop, with no error anywhere. Checking the list of enabled calendars, rather than the refresh interval, resolves that variant.

Invitations other people can see before you answer

There is a side effect of the two stricter options that is worth a look while the settings panel is open. When an invite has not been written into the calendar yet, it is pending, and a separate control decides whether people with access to your calendar can see pending invitations.

Google's documentation describes it as a toggle labelled Let others see all invitations if they have permission to view or edit my events, which appears under the invitation setting once either of the two stricter options is chosen. Turning it on is useful when an assistant handles incoming invitations, because they can act on things that have not landed yet. Turning it off is the tighter choice, since it keeps unanswered and unknown sender invites out of view. People who only have permission to see availability cannot get event details either way.

This is also the answer to a question that comes up in shared setups: an assistant reporting a meeting that the owner cannot find is not always wrong. They may be looking at the pending list.

What to change first

Start by confirming the event exists in Google Calendar on the web, then set Add invitations to my calendar to match how strangers actually reach you, and only after that look at the refresh interval on the desktop. Invitations that arrive as plain text in email, rather than as a structured invite, will never clear these gates at all, which is where a calendar that can read a pasted message and build the event from it earns its place. Caltimate handles that step on the Mac, and the wider picture of what a desktop calendar takes over is set out under Features and in the FAQ.