Manual / When something looks wrong
The banners, one by one
- For
- a controller
- Status
- current
- Covers
- the four notices that appear under the top bar
- Last checked against the app
0963ac5(2026-08-19)
Every full-width notice this app raises appears in one column directly under the top bar, on every tab, most serious first. There are four of them. This page is what each one is telling you and what to do about it.
What you are looking at
| Position | Banner | What it is about |
|---|---|---|
| 1st | Timetable feed expires / expired | The published schedule the whole app is built on is running out, or has run out |
| 2nd | Data updated | Somebody has loaded a newer timetable or roster on the server while your page has been open |
| 3rd | Pick up where I left off | An offer to reopen the view you were last on |
| 4th | … has been updated | The app itself is a newer release than the one you last looked at |
The order is the point: the first two say something about what is on your screen right now, and the last two never do.
1. The timetable feed is running out
It appears from 60 days before the loaded timetable stops covering dates, and it has two forms.
Counting down, which you can dismiss with the × on the right:
Timetable feed expires in 43 days (2026-12-31). An administrator can load a newer feed.
Expired, which has no × at all:
Timetable feed expired. The loaded GTFS feed only covers dates up to 2026-12-31, so every schedule shown is historical. An administrator can load a newer feed.
GTFS is the format the state publishes its timetables in; "the loaded GTFS feed" means the schedule this copy of the app is working from.
What to do: tell whoever administers this deployment. Nothing you can do from the app fixes it — a newer timetable has to be loaded on the server, which is a job for an administrator and takes minutes rather than seconds.
Why you cannot dismiss the expired one. Once the feed has run out, every schedule on every screen is historical. A warning that can be waved away is one that will be.
Dismissing the countdown only lasts as long as the page. Reload and it comes back, because a feed does not stop expiring because somebody closed a banner.
2. Data updated
Data updated. A newer timetable or roster has been loaded on the server. [Refresh now]
The app checks every few minutes, and says this once per page.
What to do: finish what you are in the middle of, then press Refresh now. It reloads the page — everything unsaved goes with it, which matters most if you are mid-way through drafting a diversion.
Why it matters even though nothing on screen looks wrong. The page you are reading was built from the data that was loaded when you opened it. After a reload on the server, the identifiers behind your screen can point at different things, so a page left open long enough can quietly disagree with the server about what a route or a shift is.
3. Pick up where I left off
The offer to reopen your last view: its name, its age, sometimes the caveat "The date was reset to today.", and the buttons Pick up where I left off and Start fresh. It only exists if you have switched history on, and it never moves anything until you press something.
It is explained in full on Finding your way back.
4. The app has been updated
Kinetic Melbourne OCC has been updated. 7 changes since you last looked. [What's new] ×
What's new opens the release notes for the releases you missed. The × takes it away, and counts as having seen it — it will not come back until the next release. See What is new in this release.
Why it is a banner and not a dialog that opens itself. The screen in front of you at 07:15 may have an incident on it. A new map layer has not earned the right to cover that and take your keyboard.
What they do not mean
An expired feed does not stop the live buses. The buses keep moving on the map, because that comes from a different feed. What has run out is the timetable underneath — so anything that compares a bus to its schedule, or shows you a departure time, is comparing against a schedule that no longer covers today.
With an expired feed, "today" is not today. The app can only answer for dates the loaded timetable covers, so it pins itself to the last date it has. A Timetable tab that opens on a date in the past is not a bug; it is the same fact the banner is reporting.
"Data updated" does not mean your screen is wrong. It means it might be. It is a prompt, not a fault.
"Since you last looked" is per browser. The release notice counts from what this browser has already seen. Sign in at another workstation and you may be told about the same release again. Nothing is wrong; that browser has not been told before.
None of these is an operational alert. No banner in this column is about a bus, a road or a driver. They are about the app and the data behind it. Anything about the road is on the map, in the overlays, or in the traffic radio.