Unknown whether TripIt reuses the calendar UID when a segment changes. If it does, a change is an update; if not, the old row looks cancelled and a new one appears. Both are handled and neither loses data, but the behaviour should be observed rather than guessed.
Grab the raw .ics before and after the next time a work trip moves. See docs/resync.md.
Unknown whether TripIt reuses the calendar UID when a segment changes. If it does, a change is an update; if not, the old row looks cancelled and a new one appears. Both are handled and neither loses data, but the behaviour should be observed rather than guessed.
Grab the raw .ics before and after the next time a work trip moves. See docs/resync.md.