aislop.day
TUESDAY, 9 FEBRUARY 2021

Preliminary Findings on Invite Arrival Status

A calendar invite sent by a person who uses a different calendar application has arrived in a format that creates a sequence of confirmations, none of which confirm the original thing.

3 MIN READaudio app fomo

Preliminary Findings on Invite Arrival Status Reconstructed Search History, Lightly Annotated


Search 1

"calendar invite accepted but no confirmation email"

Results: forum threads from 2018, a support article that addresses a different problem, one result that matches the description but was posted by someone using a different operating system.

Search 2

"how to tell if calendar invite was accepted by other person"

Results: instructions for checking invite response status within a specific application. The person checking does not use that application. The person who sent the invite uses that application.

The gap between these two facts is the source of the problem.

Search 3

"can sender see if google calendar invite accepted by outlook user"

Results: three contradictory answers. One says yes. One says yes, but only for certain account types. One says the response arrives but is formatted in a way that may not be recognized.

What Has Occurred

A person received a calendar invite from a colleague. The invite was sent from one calendar ecosystem and arrived in another. The recipient accepted the invite. The acceptance generated a confirmation. The confirmation was received by the recipient's own calendar system, which confirmed the acceptance to itself.

Whether this confirmation propagated to the sender is unclear.

The Actual Concern

The invite's function is to establish that two people will be in the same virtual location at the same time. This function is simple. Its execution has not been simple.

The recipient has been in the meeting for six months with this person. The meetings have always occurred. The invites have always, as far as is observable, worked.

The current invite is the same as previous invites.

The Absurd Escalation

The person has sent a follow-up message to the colleague saying that they accepted the invite and asking whether the acceptance registered. The colleague has confirmed receipt. The confirmation arrived via a different platform than the original invite.

The meeting has now been confirmed through three channels. The meeting is on Tuesday.

The Contradiction

The invite has been accepted. The acceptance has been confirmed. Whether the original sender received the confirmation is not known, but it does not matter, because the sender and recipient have since spoken and confirmed the meeting directly.

The search history exists as evidence of a problem that resolved itself through the same means available before the searching began.

Preliminary Findings Status

Preliminary. No further findings expected.

TAGSaudio app fomo
Share this