Data freshness and connection
Understand when records refresh and what to do if the connection is interrupted.
Step by step
- Returning to a recently opened list reuses its data briefly. Wallet names, public addresses, clients and tags can be reused for up to 30 seconds; the network catalog for up to 5 minutes. Balances and financial states are checked again when opened.
- The strip below the header shows the earliest successful receipt time among currently active stored-data reads. It is a page retrieval time, not a blockchain confirmation, settlement guarantee or organization-wide snapshot.
- Use Refresh visible data to request current stored records and recheck access. Individual refresh buttons still reload their own list or details. Public-node observations, exports and signing requests require their own explicit actions.
- While the tab is visible, access and eligible stale data are checked approximately once a minute, and on return to the tab or reconnection. Background checks pause while an operation is submitting or its outcome needs review.
- Changes made here invalidate related page data. Other tabs for the same organization receive an update signal; they exchange no records or credentials. A sign-in or sign-out change resets the other tab’s selected workspace.
- If an update fails, the warning and receipt time distinguish previously received data from a successful refresh. Restore the connection and choose Refresh visible data. Offline changes are not queued and are never sent automatically later.
- Signing out, changing organization, starting or ending a member preview, or changing access clears the relevant in-memory data. Reloading the page starts with an empty data cache. The application does not save organization records in IndexedDB or browser storage.