Recover from Blocked or Incomplete Work

Start with the record that is blocked and its Connections. Confirm whether its upstream and downstream documents are draft, submitted or cancelled before repeating an action. Repeating a click is not a safe substitute for checking what already posted.

No Transport Demand is created

Check that the source is submitted, supported and enabled in Transport Demand Sources. Confirm the Delivery Method's Buying/Selling/Internal applicability and who arranges transport. Check Manual versus Automatic creation, required approval state and remaining source quantities. A no-planning method is not expected to generate demand automatically through the planning event.

Do not create a new unrelated demand to get around an approval or exhausted quantity. Ask the planner to review draft loads that may already reserve the balance.

No load or vehicle appears for allocation

Check company, active allocation, submitted load state and the configured initial allocation timing. Customer loads may require submitted Delivery Notes before they enter allocation selection. Select a vehicle or category to establish capacity, then check combined weight/volume UOMs, equipment/body requirements, minimum-load rules and compatibility.

A different suggested category on the load is not by itself a reason to reject the actual vehicle. A capacity or equipment failure still is. Use Fleet Availability for the intended interval and correct its underlying reason instead of disabling compliance checks.

The loading warehouse is not known yet

For a Material Transfer request it may remain unknown on demand and on a draft load. Select a valid actual source before submitting the load. It must differ from the destination. Supplier collections use an external address; depot return pickups must respect the known custody warehouse.

Transit stock is still showing after delivery

Open the original Add-to-Transit Stock Entry and its receipts. A proof queued on a phone has not posted server stock. Check Allow Driver to Complete Depot Transfers and whether the task is Awaiting Stock Posting. If staff received manually, retain the original outgoing entry, source row, warehouse and Material Request references.

Finish remaining receipts through the same authorised path. Do not post both a manual End Transit receipt and a POD receipt for the same stock. A supplier Purchase Receipt into the vehicle needs a normal subsequent Material Transfer, not End Transit.

A return pickup has no matching stop

Select an active submitted trip in the correct company. The chosen stop must identify the same customer or depot holding the goods. Confirm the Return Request is submitted, approved as required and company-arranged. Ask dispatch to correct the route/stop assignment rather than choosing an unrelated stop.

Return Inspection will not save or submit

Check source receipt submission, the correct item/batch row, Stock UOM quantities and whether every received quantity is accounted for. Rejected groups need a reason. Every result needs a valid Target Warehouse before submission; header accepted/rejected defaults are not compulsory when the rows are complete.

If standard Quality Inspection is required, link a separate matching submitted inspection for each result group. Do not reuse the same QI for several groups. Review the exact missing-value message rather than creating another Return Request.

Cancel in dependency order

Cancel only if your role allows it and the business actually intends to reverse the recorded event. Frappe may offer cancellation of linked downstream documents; review the list rather than accepting it blindly.

Undo later stock/inspection/commercial effects where required
       ↓
Cancel dependent proof or receiving evidence when permitted
       ↓
Cancel trip, then allocation/load only if those also need reversing

Trip cancellation should not reverse valid pre-trip loading stock merely because it is linked. Conversely, cancelling a posted receipt or purchase can reopen task progress. Submitted inspection transfers must be reversed before cancelling the inspection; pickup/receiving stock can block proof reversal. Preserve links so the system can protect those dependencies.

Do not force-delete historical stock, proof or return records to clear a validation message. For an active-trip resource failure, use incident reallocation instead of cancelling the original allocation.

The driver app needs attention

Check the User/Employee/Driver link, device approval and assigned trip. Refresh after an administrator fixes approval; sign in again after session expiry. Inspect Sync Center before clearing local data or changing devices. Contact the administrator with the work reference and exact message, not another user's credentials.

[Diagram: Recovery decision tree distinguishing unsent mobile work, missing stock posting, blocked inspection and valid downstream cancellation dependencies]