1
00:00:00,080 --> 00:00:02,981
An event can disappear after an accidental delete.

2
00:00:02,981 --> 00:00:06,971
Google Calendar keeps many eligible deleted events in the calendar's

3
00:00:06,971 --> 00:00:08,421
Trash for thirty days.

4
00:00:08,421 --> 00:00:12,411
We will trace a fictional single event with no guests, restore

5
00:00:12,411 --> 00:00:14,949
it, and confirm its date and calendar.

6
00:00:14,949 --> 00:00:18,939
Do not experiment on a real meeting: deleting an event with

7
00:00:18,939 --> 00:00:21,477
guests can affect their calendars and responses.

8
00:00:22,077 --> 00:00:25,705
Create a fictional Harbor Workshop review event on an upcoming date

9
00:00:25,705 --> 00:00:29,992
you choose, from ten to ten thirty in the morning, with no guests.

10
00:00:29,992 --> 00:00:33,620
Before deletion, write down the exact date, time zone, and calendar

11
00:00:33,620 --> 00:00:35,269
name in the practice file.

12
00:00:35,269 --> 00:00:38,896
That matters because each Google Calendar can have its own Trash.

13
00:00:38,896 --> 00:00:42,524
A future date keeps this exercise usable whenever you find the

14
00:00:42,524 --> 00:00:46,151
lesson, rather than relying on a date from the publication month.

15
00:00:46,751 --> 00:00:51,215
On a computer, open Google Calendar and use the Settings gear, then Trash.

16
00:00:51,215 --> 00:00:53,619
Google's desktop help documents this route.

17
00:00:53,619 --> 00:00:56,366
Choose the calendar where the event originally lived.

18
00:00:56,366 --> 00:01:00,144
Do not confuse a hidden calendar with a deleted event: if

19
00:01:00,144 --> 00:01:04,264
you only turned off a calendar's visibility, you can show it

20
00:01:04,264 --> 00:01:05,638
again without using Trash.

21
00:01:05,638 --> 00:01:09,759
Search the deleted-event list for the exact fictional title and date.

22
00:01:10,359 --> 00:01:13,681
Select Restore beside the matching Harbor Workshop review entry.

23
00:01:13,681 --> 00:01:17,741
Avoid Delete forever, which is a different control and cannot be

24
00:01:17,741 --> 00:01:19,218
undone through this route.

25
00:01:19,218 --> 00:01:24,016
If the entry is absent, confirm the correct calendar, deletion date, and permissions.

26
00:01:24,016 --> 00:01:28,077
An event removed from a recurring series using This and following

27
00:01:28,077 --> 00:01:32,875
may not be in Trash, so do not promise recovery in every case.

28
00:01:33,475 --> 00:01:37,204
Return to the calendar and navigate to the exact future date

29
00:01:37,204 --> 00:01:39,915
you wrote down before deleting the demo event.

30
00:01:39,915 --> 00:01:43,643
Confirm the restored item appears from ten to ten thirty in

31
00:01:43,643 --> 00:01:46,694
the morning on the intended calendar, with no guests.

32
00:01:46,694 --> 00:01:50,422
The restored title alone is not enough if it appears on

33
00:01:50,422 --> 00:01:52,116
the wrong date or calendar.

34
00:01:52,116 --> 00:01:55,845
If the view is blank, check whether that calendar is currently

35
00:01:55,845 --> 00:01:57,539
hidden before assuming restore failed.

36
00:01:58,139 --> 00:02:02,265
This check proves only that one eligible fictional event was restored.

37
00:02:02,265 --> 00:02:06,390
Trash generally retains events for thirty days; a whole deleted calendar

38
00:02:06,390 --> 00:02:09,390
and some recurring-series deletions need different handling.

39
00:02:09,390 --> 00:02:13,516
If a restored invited event were real, guest responses may need

40
00:02:13,516 --> 00:02:15,016
to be collected again.

41
00:02:15,016 --> 00:02:19,516
For the practice case, the answer is the single no-guest review

42
00:02:19,516 --> 00:02:21,767
event back on its original date.
