Skip to content

Resolve Freshdesk conflicts and recover a run

Freshdesk import protects local Eos edits. A conflict needs a decision about the intended record, not repeated blind retries.

Resolve exceptions

  1. Open Customer Support > Operations > Imports > Review exceptions.
  2. Open the affected item and compare the source proposal with the current Eos record.
  3. Choose Keep Eos, Apply source or Skip as appropriate.
  4. Review the current version and confirm the decision.
  5. Retry or resume the run only after fixing its underlying issue.

For customer matches, review exact candidates. A matching company name alone does not authorize overwriting an existing company. Approved matches are checked again before use.

Source-policy holds

If Freshdesk removes or restricts a source, Eos can hold linked knowledge from external serving and AI. Expired policy verification also blocks use. Editing the local article's AI flags cannot remove that separate source hold. Use the source-policy review controls after checking the current source permissions.

Cancel or reverse

Cancel stops future work in the run. It does not roll back committed records. For reversal, open the run's reversal preview and inspect which changes remain eligible. Later edits, dependencies and access holds can block reversal. Apply only the reviewed eligible changes.

A deleted, archived or reversed destination is not silently recreated by an ordinary poll. Use explicit reimport review when appropriate. Restoring a published archived article can also require the normal editorial restore step.

Check the result

Inspect item outcomes and native destination records. Preserve the run report for unresolved exceptions. The Freshdesk reference explains checkpoints, holds and partial completion.