Notifications & support

Resolve stale records, conflicts and offline save state

Distinguish queued offline work from confirmed server writes and resolve versions deliberately.

Use this guide when Resolve stale records, conflicts and offline save state helps you follow relevant events, choose delivery channels or resolve a product issue without exposing private data.

A localized AutoNexit Sample view for this workflow. Sample data is shared and read-only.

Before you begin

  • Resolve stale records, conflicts and offline save state — Identify the affected project, record and channel and collect a safe error description; never include passwords, tokens or confidential files.

If the result is not what you expect

  • Resolve stale records, conflicts and offline save state — If nothing arrives or an action still fails, check notification preferences, browser permission, project access, offline state and available capacity.

Frequently asked questions

What should I verify before I work with Resolve stale records, conflicts and offline save state?

Distinguish queued offline work from confirmed server writes and resolve versions deliberately. Identify the affected project, record and channel and collect a safe error description; never include passwords, tokens or confidential files.

How do I know Resolve stale records, conflicts and offline save state is complete and trustworthy?

A good result either delivers the intended notice, records a private support request or explains the exact permission, conflict or capacity condition. If nothing arrives or an action still fails, check notification preferences, browser permission, project access, offline state and available capacity.

Was this guide helpful?

Need help with your own project?

Sign in to send a private support request. Do not include passwords, tokens or private files in the first message.

Open support

Help topics

On this page