If your deletion stops before completing, do not panic — WipeAway is designed to handle interruptions safely. Events that have already been deleted will not be deleted again, and you can resume from where the process stopped.
Common causes of an interrupted deletion
- Internet connection dropped — WipeAway communicates with Google's servers throughout the process; a dropped connection will pause it
- Browser tab closed or refreshed — accidentally closing the tab or navigating away will interrupt the deletion
- Session expired — if you have been signed in for more than 24 hours, your session will have expired
- Mobile browser suspended the tab — some mobile browsers suspend background tabs to save battery, which interrupts the process
- Temporary Google API issue — Google's Calendar API occasionally experiences brief slowdowns or interruptions
How to resume after an interruption
- Go back to wipeaway.app
- Sign in again if your session has expired
- Select the same calendar(s) and the same cut-off date
- Click Count entries — the count will now reflect only the events that have not yet been deleted
- Review the updated count and confirm to continue the deletion
Because WipeAway only deletes events that still exist, you will never accidentally delete anything twice.
The count changed. If you see a lower event count than before, that is correct — it means some events were already deleted before the interruption. The remaining count shows what is still left to clean.
If the deletion keeps stopping repeatedly
If the deletion is stopping after only a few events every time you retry, this may indicate a persistent Google API issue with a specific event. Contact us with the calendar name and the approximate event count — we can help investigate.