OdyCust/ GUIDE
УКР

Data freshness and connection

Understand when records refresh and what to do if the connection is interrupted.

Step by step

  1. Before opening the application, a short service check must succeed. While this tab is visible, availability is checked every 60 seconds. A failed check shows We’ll be back shortly; retries wait 5, 10, 20, then up to 30 seconds. Hidden tabs pause these checks and reconnecting wakes them.
  2. During the maintenance screen, new API requests and background data refresh are paused. A healthy service check returns you to the page without submitting an action again. Normal access checks still apply; availability alone does not confirm a payment or database operation.
  3. The bottom API strip shows only round-trip latency and the last nine characters of the backend commit, without a hover tooltip. Refresh API status checks the same /health probe without repeating an operation. The indicator marks responses from 1000 ms as slow; an unavailable API shows its status. Build time, measurement time and UI contract are omitted. This probe checks the API process, not database readiness.
  4. This also applies to the mobile or desktop app sign-in confirmation page. If the service check fails between sign-in steps, the next request is not sent. After recovery, restart sign-in manually; confirmation is never submitted automatically.
  5. This device saves balances for up to 5 minutes and wallet, address, customer, tag and token lists for up to 15 minutes. Reloading can reuse fresh data after your current access is verified. Each balance shows its observation time; use its refresh button for a new reading.
  6. The header refresh icon requests current visible stored data. Its accessible status reports the receipt time; this is not blockchain confirmation, settlement or a single organization-wide snapshot.
  7. 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.
  8. While this tab is visible, access and eligible stale data are checked about every two minutes. Returning sooner does not repeat those checks. Reconnection and data changes can refresh sooner. Background checks pause during protected operations.
  9. 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.
  10. 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.
  11. Signing out or an access failure clears the display cache. Different organizations, accounts, access and interface previews cannot reuse each other’s data. IndexedDB also contains separate unfinished-operation journals; clearing display data preserves those original requests. Language and appearance use localStorage. Credentials, private keys, quotes and signed artifacts are never cached.
  12. On desktop, the compact data-freshness indicator sits in the fixed header. On narrow screens its status remains available to assistive technology beside the refresh control. The main content scrolls between header and footer; navigation fits the sidebar or moves into its additional-sections menu.

Related reading

OdyCust · User documentation2026-10-13

Search documentation

Search stays within this guide. It does not request console data.