Skip to content

Set the task list to refresh itself

Making the board and the task list update on their own, instead of pressing refresh.

Automatic refreshing is off unless someone turns it on. If your board is not updating by itself, that is the expected starting state rather than a fault.

  1. Open Dispatch.
  2. Open DispatchSettings from the toolbar.
  3. Find the refresh intervals. There is more than one:
    • the board — the job list itself
    • the tasks — the task list (on the rebuilt Dispatch page only)
    • the driver locations — the map
  4. Pick an interval for each one you want updating on its own. The choices run from 30 seconds up to 15 minutes, in 30-second steps. Disabled is also in the list, and is what each one is set to until you change it.
  5. Save.

A shorter interval is not automatically better. Every refresh is a request to the server, and on a busy board a very short interval can make the screen feel worse rather than better. 30 seconds is a reasonable starting point; lengthen it if the page feels heavy.

This is the part worth understanding, because it looks like a fault and is not.

The interval is remembered in your browser, on that computer, for your login — and nowhere else. It is not stored on your company’s account.

So it will appear to reset to Disabled whenever:

  • you use a different computer
  • you use a different browser on the same computer
  • you use a private or incognito window
  • your browser data is cleared, by you or by an IT policy
  • someone else logs into the same computer with their own login

When the saved value cannot be found, the setting falls back to Disabled, silently. Nothing warns you, and the board simply stops updating on its own.

Automatic refreshing starts off, and the setting is always per-person, per-browser. Whether you get a separate Tasks interval depends on which Dispatch page you are on — the rebuilt page has one; the previous page refreshes tasks along with the board. See Dispatch for how to tell which page you are on.

You set it and the board still is not updating. Confirm it saved by reopening the settings — if it reads Disabled again, the value is not being kept, which usually means browser storage is being cleared.

It works on one machine but not another. Expected. The setting does not travel with your login.

The task list is not refreshing but the board is. On the rebuilt page they are separate settings. Set the Tasks interval too.

Internal: how this page was verified draft
Checked by
kenneth on 2026-07-31
How
source-check
Where
none · logged in as not-applicable
Against
  • despatchweb wwwroot/app/components/home/home.controller.ts:91-92 — the interval is stored under localStorage keys refreshInterval-<page>-<ContactID> and driverLocationRefreshInterval-<page>-<ContactID>
  • same file:379-395 loadSavedRefreshInterval — reads localStorage; auto-refresh only starts when a saved value above zero is found
  • despatchweb .../dashboard-settings-dialog.service.ts:109-114 — when no value is present the selection defaults to {id: 0, text: 'Disabled'}
  • despatchweb wwwroot/app/functions/MinsSelectionOptions.ts — options run from 30s to 15 minutes in 30s steps
  • despatchweb .../dashboard-settings-dialog.service.ts:97 — the interval is only shown on the Dispatch and Domestic pages
  • despatchweb .../dashboard-settings-dialog/DashboardSettingsDialog.tsx:49 and the React module — a separate showTaskRefresh / selectedTaskRefreshInterval exists on the rebuilt page; the previous page has no separate Tasks cadence
Likely to change
high — The Dispatch page is mid-replacement. The rebuilt page carries a separate Tasks interval that the previous one does not, so what a reader sees depends on which page they are on.
Re-check by
2026-08-31 — overdue
Config-dependent
1 item(s) called out on this page
Screenshots
1 still to capture
Open questions
  • The exact wording and position of the controls in the settings dialog have not been seen on screen.
  • Whether the rebuilt page stores its intervals the same way as the previous one. The previous page's storage is confirmed; the rebuilt page's has not been traced.