> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/customers-and-work/scheduling/resolve-scheduling-conflicts.md).

# Resolve scheduling conflicts

Scheduling can be blocked for two different reasons, and the visit form tells you which one you hit.

## Scheduling conflict

Property-based visits can overlap on a technician's schedule without a numeric limit. A no-property availability block, such as Tech Unavailable, remains exclusive: neither a property visit nor another availability block can overlap it. The conflict message identifies the existing visit or block. Commute time also counts, so a drive that crosses into unavailable time is rejected.

![Scheduling conflict message in the visit form](/files/1YgBee6cZ7shc0sG5X26)

## This pushes a visit into the next day

A visit is allowed to run past midnight, but no visit may *start* on the next day. This message means your change would push a later visit's start time past midnight — usually because an earlier visit grew or moved and everything after it shifted. Drive time counts too: a visit starts after the technician's previous visit ends *plus* the drive to get there, and when that drive is what carries the start past midnight, the message says so and shows the drive time.

![Next-day message in the visit form](/files/oSsvjiK7pi52UDPXfedY)

## When they appear

Both appear when you save the visit form. Dragging a visit on the calendar shows a conflict as a message at the top of the screen; a drag that would push a visit into the next day is refused with a general "couldn't schedule" message rather than the detailed one above, so re-check the technician, the start time, and the visit duration if a drag is rejected without explanation.

## Common fixes

Move the visit to another time, assign a different technician, adjust duration, or return the visit to the backlog until the office can confirm the plan. For a visit pushed into the next day, start it earlier, shorten it, or move the later visits to another day. For multi-day or all-day edge cases, review the exact start and end time carefully.

> **Where to find it:** Scheduling page, while dragging or editing a visit

## Related guides

* [Drag and drop to schedule, move, reassign, and handle conflicts](/customers-and-work/scheduling/drag-and-drop-to-schedule-move-reassign-and-handle-conflicts.md)
* [Schedule, reschedule, or reassign a visit](/customers-and-work/scheduling/schedule-reschedule-or-reassign-a-visit.md)
* [Deleting a scheduled visit is permanent](/customers-and-work/scheduling/deleting-a-scheduled-visit-is-permanent.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.withessential.com/customers-and-work/scheduling/resolve-scheduling-conflicts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.