Duplicate calendar entry or double booking? Check the source

Two bars cover the same dates in a rental calendar. It is tempting to remove one and make the screen look right. Before doing that, establish what each bar represents: the same stay reaching your view twice, a separate availability restriction, or two actual reservations that cannot both be honoured in the same home.

The distinction determines the next action. A display or import problem calls for tracing records and connections; a real booking conflict needs prompt handling of the reservations. Neither is resolved safely by deleting the first entry that looks redundant.

Trace both entries to the original records

Start with the correct rentable unit, not just a similar listing name. Open each entry's source where available and compare its platform, arrival, departure and current status with the original booking account. Keep any reservation references in your private working notes. An event title or a colour is a clue, not confirmation of a separate guest.

Airbnb's calendar-sync guide explains that connected calendars carry booked nights and some availability blocks. Consequently, a closed interval in another calendar should be investigated before being counted as an additional reservation.

Write down the direction of each connection that could supply the interval. Check whether a local reservation record and an imported event describe the same original booking, or whether two feeds are being mistaken for two independent sales. Matching dates alone are not enough: different guests can book the same dates, while one changed reservation can have stale dates in a receiver.

For a technical investigation, the iCalendar specification's UID section defines an identifier for a calendar component. Use that as evidence for tracing an event, not as a substitute for checking the booking record. Do not edit identifiers in a feed as a quick fix or publish complete feed URLs in a support request.

Illustrative comparison: the original account confirms one stay arriving Tuesday and departing Friday. Two calendar representations cover that same stay. The occupied nights are still Tuesday, Wednesday and Thursday: three nights, not six. This conclusion depends on confirming that there is only one actual booking; it cannot be inferred from the matching bars alone. Check the departure-day boundary if one view appears to extend the stay.

Classify what the evidence actually establishes

Use the original records to choose the branch. Here, a booking means a currently confirmed, uncancelled reservation. A conflict requires two such bookings for the same rentable unit sharing at least one occupied night. A duplicate means that both entries have been traced to the same original stay.

If a source cannot yet be checked, leave the classification unresolved. Do not reopen a known occupied night just because the second entry has an unclear label. The blocked-date review helps separate reservations from other restrictions.

Resolve the right layer, then check the next stay

RentTools imports calendar events by property and platform, using the event identifier during reconciliation. That does not mean every similar-looking entry from different sources is a separate booking, or that arbitrary overlaps can be merged automatically. Check the source relationship before changing a local record.

Do not remove a calendar connection merely to clear the view. Removing a RentTools link also removes that platform's imported events for the property. The screen may look quieter while you have actually removed useful availability evidence. If a connection is wrong, review the feed-replacement checklist and protect affected nights while correcting the identified connection.

When an original reservation has changed, compare its current dates with each receiver after the next import. If one view remains stale, investigate that update path rather than creating another guest booking to compensate. Correct only the record or setting whose role you have established; keep a note of what changed so another team member does not repeat the cleanup.

For two genuine bookings, keep both original records visible to the person handling the conflict. Contact the relevant platform support and the affected guests with accurate information as appropriate. This guide does not promise a fee waiver, refund amount or relocation outcome.

Finish by checking the selling calendars and the preparation plan. Confirm the intended occupied nights remain unavailable, unrelated holds remain intact, and the actual departure has one agreed cleaning plan with a named responsible person. Two calendar bars are not a reason to send two cleaners, and a tidier calendar is not proof that the next arrival is ready.