Skip to main content

Keep capturing when the connection drops

Alkax can queue supported place changes on the device and send them when connectivity returns.

An Alkax offline workflow showing capture, local queueing, reconnect, and sync.

Capture first, keep work safely queued on the device, then let Alkax sync when connectivity returns.

While offline​

  1. Capture the location and enter the place details.
  2. Save the item to the pending queue.
  3. Keep the browser data on the device; clearing site storage can remove unsent work.
  4. Review the offline indicator and queue count.

When connectivity returns​

Alkax attempts to sync queued items. Keep the app open long enough to see the outcome.

An item can still require attention if:

  • a similar place was added while you were offline;
  • a field no longer passes validation;
  • authentication expired;
  • an image cannot be uploaded;
  • the server rejects the change.

Do not repeatedly create the same place because it still appears pending. Review the queue status and nearby search results first.

Field checklist​

  • Load the area and sign in before leaving reliable connectivity.
  • Confirm that the device has enough available storage.
  • Use precise, stable descriptions while the context is in front of you.
  • Review the queue before ending the field session.
  • Sync on a trusted connection as soon as practical.
  • Search for duplicates after a long offline period.

Offline support reduces data loss; it does not guarantee that every map resource or third-party navigation service will be available without a connection.