Review the Driver schedule
The Schedule view in Profile displays the schedule already present in the current Driver session. It is a read-only presentation with seven weekday labels, next calendar dates, enabled intervals, or Not available. It does not prove that the schedule is current, persisted, server-enforced, or sufficient for work eligibility.
:::warning A full-day fallback is not a real schedule
When Driver App receives no schedule value, the view creates a local fallback showing every day from 00:00 to 23:59. Treat that only as missing-data presentation. It is not authorization to sign in, become available, accept an order, or work all day.
:::
Availability
The Schedule row is visible in the Driver Profile. Selecting it opens a modal with a Schedule header and Back control. The view has no edit, save, override, publish, or operator-contact control.
Opening the modal uses the schedule already held in local session state. It does not automatically request a fresh schedule. Pull-to-refresh can request a user refresh separately.
State and result matrix
| Visible state | Safe interpretation |
|---|---|
| Seven weekday rows | The local schedule array supplied seven display items or the missing-value fallback was used |
| Enabled day with one interval | The returned/local day contains one lapse with open and close time |
| Enabled day with several intervals | The local day contains multiple lapses; they are displayed in source order |
| Not available | The local day item is disabled |
| All days 00:00–23:59 | No schedule value was supplied and Driver App rendered its all-day fallback |
| No weekday rows | An empty schedule array was supplied; the missing-value fallback does not run for an empty array |
| Current date banner | Device/local date formatting at render time |
| Day date | The next occurrence of that weekday calculated from the device date |
| Pull-to-refresh gesture | Driver App requested user refresh; completion and changed schedule are not proved |
| Back to Profile | The local modal closed; no schedule or account mutation occurred |
Seven-day display boundaries
Weekday labels run Sunday through Saturday. Enabled intervals are formatted as
zero-padded 24-hour HH:mm values. Disabled days show Not available instead
of intervals.
The view does not show an explicit schedule timezone. It formats stored hour/ minute values and calculates displayed dates from the device clock. Device timezone, account timezone, server time, daylight-saving changes, locale, and schedule ordering can differ.
A malformed or short schedule can produce fewer rows or a render problem. The view does not establish a safe complete fallback for every malformed shape.
Refresh and persistence boundaries
Pull-to-refresh calls the current-session user refresh. The refresh indicator is not tied to a loading receipt in this view, and the modal does not display a schedule-specific success or error result. A gesture, unchanged row, or changed row does not prove which backend revision was read or persisted.
The schedule display has no editor. Schedule changes belong to an adjacent account/operator workflow and a consequential user-update contract. Such an update can affect availability, history, jobs, sockets, and schedule gates. This view neither performs nor certifies that persistence.
Effects and boundaries
Keep these concepts separate:
- The schedule shown in Profile.
- The local sign-in schedule gate.
- Current Driver availability.
- Busy state and assigned orders.
- Account/project schedule policy.
- Server-side schedule and timezone.
- A future user-update/persistence result.
The Profile schedule is not a reservation, shift assignment, automatic unlock time, availability receipt, or authorization for an order action.
Troubleshooting
Every day shows 00:00–23:59
Treat this as the missing-schedule fallback, not an all-day work schedule. Ask the operator that owns the Driver account to confirm the persisted schedule.
No days are shown
An empty schedule array does not trigger the fallback. Close the modal and ask the schedule owner to review the account; do not infer unrestricted access.
A day or time looks incorrect
Compare the displayed device date with the account/operator schedule and timezone. Do not change the device clock or availability to make the view match.
Pull-to-refresh appears to do nothing
The view does not expose a refresh-loading/result receipt. Do not repeat the gesture as a currentness test. Return to Profile once and ask the operator to confirm the source schedule.
This schedule differs from the sign-in gate
The Profile display and local schedule gate have different presentation and failure boundaries. Review Understand the Driver schedule gate and do not treat either screen as server eligibility.
Related guides: View the Driver profile · Understand the Driver schedule gate · Change Driver availability · Navigate Driver App