---
metadata:
- name: generator
content: Diplodoc Platform v5.19.6
alternate:
- https://docs.routeq.com/doc/en/delivery/functions/idle.md
title: RouteQ — functions — courier downtime
---
> **Documentation Index:** Fetch the complete configuration index at https://docs.routeq.com/doc/en/llms.txt
# Courier downtime
Downtime occurs when a courier spends a long time in one place without moving along the planned route. This usually means there's a problem that can lead to delays or losses.
There are different types of downtime:
**Outside a location**
: A long stop between two locations on a route (such as a depot and a delivery address).
**At location**
: A long unplanned stop at a delivery location, depot, or other location along a route.
## Settings {#idle-setting}
{% note info %}
To change parameter values, contact support. Values apply to the entire company.
{% endnote %}
### Period before downtime begins {#idle-time}
The `idle_time_window_s` parameter defines how long someone must be idle before downtime starts.
Default value: `1800` (30 minutes).
### Downtime start {#idle-type}
The downtime detection method depends on the `node_idle_type` parameter.
**Delivery window**
: Set the `node_idle_type` parameter to `time_window_end`.
Downtime begins as soon as the delivery time window ends if the courier arrived at the delivery location on time or before the order time window started.
{% note info %}
If the courier was late and arrived after the order time window ended, downtime is counted as soon as they arrive.
{% endnote %}
**Handover time**
: Set the `node_idle_type` parameter to `service_duration` (default value).
This detection type is related to the [estimated time of arrival (ETA) calculation type](https://docs.routeq.com/doc/en/extras/sms-setting.md):
- `arrival_time`
Downtime detection begins as soon as the courier arrives at the delivery location.
When the courier arrives, downtime begins when the handling time `service_duration_s` and the period before downtime begins `idle_time_window_s` have passed, even if the order time window hasn't ended yet.
- `delivery_time`
Downtime doesn't begin before the order time window starts. Time when the courier is standing still while waiting for the order time window to begin isn't taken into account.
If the courier arrives before the delivery time window starts, then downtime begins after the order time window begins and after the handling time and the period before downtime begins `idle_time_window_s` end.
If the courier arrives after the delivery time window starts, then downtime begins when the handling time and the period before downtime begins `idle_time_window_s` end.
## Viewing downtime{#idle-display}
You can view downtime data in [Routing Workspace](https://yandex.com/courier/) when you get coordinates from the courier.
### Notification window{#notifications}
Notifications promptly inform you when a courier has stopped moving. They appear in the upper-right part of the screen when downtime is registered.
The notification card contains:
- Information about the courier and downtime duration.
- An **Open route** button to go to the route page.
- A **Contact courier** link to start a chat with the courier in Yandex Messenger.
- A button to close the window.
Multiple notifications are displayed on top of one another.
Notifications are disabled by default. To enable notifications:
1. Go to **Settings** → **Company**.
1. Enable the **Downtime notifications** option.
### Route page {#route-page}
The route page displays:
1. The time when the courier last sent coordinates.
1. The courier's position when they last sent coordinates.
This way, you can see where the courier is and how much time they spend at each location on the route.
Using the time when the coordinates were last sent, the logistics coordinator can determine whether a courier is having connection issues and contact them if necessary.
## Downtime statistics{#idle-statistic}
You can find information about downtime on completed routes in the [Courier performance report](https://docs.routeq.com/doc/en/delivery/interface/quality-report.md) in the **Downtime outside of location** and **Downtime at location** fields.
{% include [warehouse-feedback](../_includes/feedback-7b71896f9bc3.md) %}