This feature allows you to define reasons and collect data on why specific Tasks were not able to be executed. Failure reasons will be stored within the Task History, and you can further analyze the failure reasons within the eLogii Analytics feature,

To be able to collect data on Task Failure reasons, Drivers must have the ability to fail Tasks from the Driver app. Enabling the Driver to mark a Task as failed in-app can be done in Configuration ⇒ Task Issue Workflow ⇒ Allow Driver to Mark Task Failed.

Click Save once the feature has been enabled.

Enabling this option will show a list of selectable reasons in the Driver app before failing the Task.

Setting this up for both pickup and delivery can be done in Configuration ⇒Task Issue Workflow ⇒ Task Failure Reasons.

The failure reasons can be anything you frequently encounter such as "Contact was not present", "Wrong address", "Missing component" and so on. When failing the Task, the Driver can select any of the provided options.

If you would like to allow the Driver to have more freedom with reporting why a Task could not be completed, It's also possible to add a custom Task failure reason.

As mentioned previously, it's possible to view all failed reasons for Tasks either on an individual level or on a broader level by utilizing the Failed Reasons section in Analytics.
​

Filters can be adjusted to modify the view to your liking. You can filter by a specific period in the past and combine it with filtering through specific Teams, Drivers, or Customers.

Additionally, if you want to see the failed reasons immediately before eLogii Analytics processes the data, you can find them in the Task History section,

Failed reasons are also exportable via CSV.