Diagnose calendar problems
Trace a finding to source evidence and decide whether a safe repair is possible.
Updated · Applies to: ICS ViewerFollow the evidence
Open a finding and read: what was found, where it appears, what may happen, and what CalendarLint proposes.
Use Source to confirm the cited line. Use Calendar or Events to see whether the problem changes what a person will experience.
Classify before repairing
- Mechanical: file boundary, line ending,
VERSION, or other deterministic syntax. Usually safe to fix. - Missing intent: unknown time zone, missing timestamp, or ambiguous local time. Get publisher context.
- Relationship: duplicate
UID, recurrence exception, or attendee update. Inspect all related components first.
Severity describes possible impact, not certainty. Evidence quality tells you how strongly the conclusion is supported.
Record uncertainty
Choose Leave unchanged when the intended value is unknown. A visible unresolved finding is safer than a plausible-looking invention.
Then continue to Repair, compare, and download.