Reload when an application update is available

When an update is available, the new Astrato application shows a notification at the bottom right: An update is available. Reload to get the latest version. It can appear on any page, including the lobby, workbooks, administration and the Semantic Layer Editor. It appears only in the main application page, never inside an embedded editor or other iframe.

Choose What’s new to read the release notes in a new tab before you reload. The notification stays where it is.

The notification keeps clear of Nash’s message box and its Send button. While Nash is open in that corner, the notification moves beside Nash, narrower if it needs to be to stay clear of the navigation on the left. When there isn’t room beside Nash, it moves just above the message box.

The application checks every five minutes while your tab is visible. It also checks immediately when you return to an already open tab or when your connection comes back online while the tab is visible. The notification stays until you reload or dismiss it. It never reloads the page for you; the page reloads by itself only when part of it can’t load after an update.

Save any unfinished work before choosing Reload: it reloads the current page immediately, without an application confirmation dialog, and can lose unsaved changes. Existing browser warnings about unsaved work still apply; cancelling one keeps the notification available.

Choose Dismiss to hide the notification for that update. No update indicator remains. When browser storage is available, dismissal applies across tabs on the same site and survives reloads. Clearing that site’s browser storage clears the remembered dismissal. If storage is blocked, dismissal lasts only in the open application. A different update may notify you again.

This notification is available in the new application, not the legacy interface. A tab can detect later updates only after it has loaded a version of the application that includes this notification.

When part of a page can’t load after an update

A tab opened before an update can’t load parts of the application it hasn’t shown yet, such as Compare, the Developer view, a chart in Nash or a Data App’s source. When you open one:

• If nothing in the tab is unsaved, the page reloads once by itself and opens the latest version.
• Otherwise, the notification changes to Astrato was updated. Save your work, then reload to continue. Save your work, then choose Reload.

Unsaved work includes editor changes not yet saved, unsaved Data App source edits, Developer view edits not yet applied, a message typed to Nash but not sent, and a Nash reply still being written.

The page reloads by itself at most once a minute. If a part still can’t load straight after that reload, the notification reads Astrato was updated. Reload to continue. instead. Dismissing it hides it until you reload. Inside an embedded editor, where the notification never appears, the part itself says it could not be shown and offers Reload.

If Astrato can’t finish loading when you open or reload a page, it tries once more by itself. If that also fails, the page shows Astrato couldn’t finish loading with Reload.

Lobby navigation

When the new lobby is enabled for your workspace, it becomes the default. When disabled, direct links to its pages return to the original application. While enabled, ordinary links to original lobby pages redirect to their new equivalents. Links to individual System Settings tabs open the matching tab in the new lobby. The Semantic Layer Editor and workbook editor retain their own routes and access checks. Disabling the new lobby also redirects open pages after the application receives the updated setting.

Workbook links from the new lobby open the editor and viewer in the connected Astrato application.

When the new lobby is enabled, open the user menu in the top right of the original lobby and choose Switch to new lobby. In the new lobby, Switch to old lobby opens the original Workbooks page. The return option is hidden when your workspace requires the new lobby. Switching applies to that visit only and does not change your workspace’s default lobby. Refreshing, reopening a bookmark or entering an original lobby address opens the new equivalent. Links for features that still require an original screen open that screen deliberately, including when the manual switch is unavailable. Copying those destination addresses does not preserve the exception. A blocked new tab or blocked site storage prevents switching and shows an error. When a fallback requires provider sign-in, its matching authorization response returns to the original integration screen to finish setup. Start sign-in again if the attempt has expired.

New-application links use /web/ by default, including /web/sle/ for the Semantic Layer Editor. Workspaces explicitly configured for the previous layout keep /sle/ links. Existing links in either layout continue to work.