What Google Calendar's help page says
This error usually happens when Google Calendar can't read some events in your file.
Google Calendar only works with files created by major calendar applications like Microsoft Outlook, Apple Calendar, and Yahoo Calendar.
If you exported your file from one of these applications, try exporting it again and re-importing it into Google Calendar.
Quoted word for word from Google Calendar's help page, listed under Sources.
Why it happens
- Some events in the file are written in a way Google Calendar cannot read. Its page does not say which lines or properties it rejects.
- The file came from an app other than the ones Google's page names, such as a booking system or a script.
- A possible cause that Google does not name is a file edited by hand, for example split to get under Google's 1 MB import limit, so that an event lost its start line or its END:VEVENT line.
How to fix it
- Export the calendar again from the original app and import the new file, as Google's page suggests.
- If the count is still short, drop the same .ics on the ClientHours Google Calendar page. The warnings above the timesheet name each event it could not read.
- Open the .ics in a text editor and search for one of those titles. Compare its lines with an event that imported, starting with DTSTART and DTEND.
- Fix or delete that event, save the file and import it into Google Calendar again.
Google Calendar to timesheet by client
What ClientHours does with the file
- An event with no readable start is left out, and a warning names it. A test event titled "No start here" got the warning "No start here" has no readable start time and was left out.
- An event whose end time cannot be read is named too. It is kept with no end, so a timed one counts zero hours and appears under "Left out" as zero length.
- A file that stops partway through an event gets a warning that it may be cut off. The unfinished event is not counted.
- Lines with no colon in them cannot be read. They are skipped and the warning says how many. Tasks and journal entries are skipped and counted as well, since only events count as time.
Limits
- The warnings list what ClientHours could not read. Google may reject other events for reasons its page does not give, so the two counts can differ.
- Events are named by title. Two broken events with the same title look alike in the list.
- ClientHours does not write a repaired .ics file.
- ClientHours has not yet been run on a real Google Calendar export. Its test calendars are built by hand from the iCalendar standard and Google's help pages, so check the first timesheet against your calendar.
Questions
- Does Google say which events failed?
- Its help page does not. It says the error usually means Google Calendar cannot read some events in the file, and suggests exporting again from Outlook, Apple Calendar or Yahoo Calendar.
- Are repeating meetings the problem?
- Google's page says some apps export repeating events as a collection of single events, which then import as single events. That changes how they look after the import. It is not named as a cause of this message.
- Can I bill from the file even though Google skipped events?
- ClientHours counts every event it can read in your dates, whether or not Google imported it. Check the warnings first, because any event named there is missing from the hours.
Sources
Other import problems
- Clockify: "Date, time, and duration formats don't match Clockify settings"
- Clockify: "The file is not comma-delimited"
- Clockify: "Missing or incomplete field values"
- Toggl Track: "Adding new users increases your workspace fee"
- Toggl Track: "Not allowed as header: Project;task;client"
- Harvest: semicolons "will result in import errors"
- Google Calendar: "Processed zero events"
- "Google Calendar is temporarily unavailable" when importing
- Google Calendar: "Feed processing error"
- Calendar and time tracker import problems
ClientHours is free, with no account and no payment. The calendar file never leaves your browser.