Purpose

Prerequisites

  • Read the notification actually shown in your session.
  • Check for unfinished orders, forms or other unsaved work before using Reload.
  • Save or finish that work first where possible. Reload is not a save action, and unsaved changes can be lost.

Steps

  1. When an update notification appears, read its warning before selecting an action.
  2. Check your current task for unsaved changes. Save or finish it first where possible; do not rely on the update action to preserve it.
  3. Choose Reload only when you are ready to reload the application and accept the risk to unsaved changes.
  4. Wait for the page to load, then reopen the relevant task and verify its saved state before continuing.

Fields and controls

  • Update notification — indicates that the application is offering a reload for an update. It is not confirmation that your work was saved.
  • Reload — reloads the application. It does not submit an order, save a form or confirm a completed business action.

Expected result

The application reloads. Verify the page and the saved state of your work after it opens; the notification alone does not prove that every update or recovery step succeeded.

Limitations

  • Some versions show a warning notification rather than a persistent banner.
  • A notification can reappear after another notification replaces it. Its return alone does not prove a new update or a failed save.
  • Availability and timing depend on the application version and browser session. There is no guaranteed update-delivery interval in this guide.
  • Do not assume loading-error recovery preserves unsaved work or always succeeds.

Errors and recovery

  • If the page remains unusable or repeatedly reloads, stop retrying actions that could submit duplicate work and contact Support with the visible message and affected task.
  • If an order or save result is uncertain, inspect the saved record before repeating the action. A reload is not proof that the earlier action succeeded or failed.