When a delivery is not made, and it does not have ATL (Authority to leave), the driver will usually start a return request on the App. This article explains how a return request can be handled when it happens.
You will see the requests on the "Jobs" page from the left@ nav. A new tab in the orange shows the number of return requests that need to be handled.

Click on the "Handle return request" button on the right-hand side of a job,

Follow the prompts to make decisions on what you would like to do.

If you usually expect returns to occur, we recommend you tick the "Return to store" option when creating a timeframe. This will allow the algorithm to set the origin as the last destination when planning the run.