Review logistics assignment requests
Some Driver App configurations can add a logistics-request entry to Orders. Use it to review available assignment cards and open a request detail before you decide what to do.
This procedure is pre-action only. Do not select Accept, Reject, a delivery-time control, or any order-status control while following it. A visible request, card, or detail does not prove that the request is still pending, eligible, unlocked, assigned to you, or accepted by the running service.
Availability
The logistics entry is source-defined when its raw configuration value is truthy and the app is not using the combined order-tab presentation. A non-empty configuration value can be treated as truthy even when an operator might read it as disabled. Visibility therefore does not prove intended enablement.
The list also depends on an authenticated driver session, connectivity, current request data, and provider state. Expired requests and empty returned groups are removed from the visible list. The API source applies driver self-scope, role, request ownership, pending/time-window, and other eligibility rules separately.
Before you start
- Open the authenticated Orders area.
- Confirm that the logistics-request icon is visible.
- Use synthetic or non-sensitive support evidence only; request cards and details can contain private business, customer, order, timing, location, and contact information.
- Stop before every Accept, Reject, ETA, status, map, contact, or message action.
Opening the list or detail can start reads, GPS/location work, realtime subscriptions, remote assets, and other provider behavior without a decision button being pressed. Screen review is not a hermetic runtime test.
Complete the task
- Select the logistics-request icon in Orders.
- Wait for the list to show loading, available cards, empty, or error state.
- Review only the visible request summary. Distinguish an individual request from a group presentation.
- Select the request card, or View order when that control is shown, to open its registered logistics detail.
- Review the header and available order information without selecting a decision or order action.
- Use the detail's back control once to return to the request list.
The detail can show Accept and Reject for eligible-looking states. Those controls are not part of this procedure. In current client source, a rejection path can navigate back before its request settles; an accepted group can also lead to separate per-order ETA writes. Do not use navigation as confirmation of a decision.
Verify the result
The safe observable result is limited to one of these states:
- the logistics list is visible with loading, cards, empty, or error content;
- one registered logistics detail is visible; or
- the prior list is visible after using back.
No assignment, order, group member, ETA, location, message, socket, notification, or provider result is verified by this review.
States and variations
| Visible state | Meaning | Safe next step |
|---|---|---|
| Logistics entry absent | Configuration, combined-tab presentation, account, or current client state did not admit it. | Ask the configuration owner; do not force a route. |
| List loading | Assignment read has not settled. | Wait for cards, empty, or error. |
| Available card | The current client result contains a non-expired request. | Review the summary; eligibility remains server-owned. |
| Grouped card | The result contains a group presentation with member orders. | Open only to review; members can have distinct outcomes. |
| Empty | No non-expired displayable request remains in the current result. | Do not infer that no request exists elsewhere or will arrive later. |
| Error | The read did not produce usable data. | Stop; do not retry a decision. |
| Detail loading | Detail and related reads are settling. | Wait for content/error; do not press actions. |
| Detail populated | Header/content and conditional controls are visible. | Review only; use the relevant decision guide later. |
| Removed/locked/expired update | Realtime or a later read changed the request while visible. | Return to the list and do not act on stale content. |
| Back after review | Prior navigation state is visible. | This confirms navigation only, not cancellation or server state. |
Troubleshooting
| What you see | What to check | Safe recovery |
|---|---|---|
| The logistics icon appears when configuration looks disabled | The client uses truthiness rather than an explicit enabled-value comparison. | Leave requests untouched and ask the configuration owner to verify the intended setting. |
| A request disappears | Expiration, lock, ownership, realtime update, list refresh, or another assignment decision can change visibility. | Do not reopen it through a notification or private link; recheck the current list once. |
| Detail keeps loading or shows an error | Assignment/detail/business/message/location/provider reads can settle separately. | Return once if available and report the visible state without request, order, customer, or location data. |
| Detail says you were removed | The returned order no longer has the current Driver relationship expected by the client. | Accept the warning and return; do not select a decision control. |
| Back occurs after a decision was pressed accidentally | Navigation can happen before the decision request settles. | Do not repeat the action. Escalate immediately with sanitized time/state and let the assignment owner verify the server result. |
| A group appears partly updated | Assignment and per-order ETA/order follow-ons are not one proven atomic operation. | Stop and ask the assignment owner to reconcile every member; do not repair from the app. |
Related guides: Driver App overview · Navigate the Driver App · Active delivery · Location permissions