Resolve Guide project conflicts and recovery

The project status icon opens diagnostics, conflicts, and saved recovery material for the current Local Guide Project.

Resolve current problems

1. Select the project status icon to open Local Guide Project.
2. Read the diagnostic's file, location, and message.
3. Correct invalid JSON or missing references in your text editor.
4. Save or cancel an overlapping unsaved CareMap dialog draft.
5. For a conflict, compare Current CareMap value with File proposal.
6. Choose Use CareMap version or Use file proposal, then verify acceptance.

Independent property edits can merge. Competing changes to the same field or ordered list require review. A stale edit to rich content can also conflict with newer wording or formatting.

Use CareMap version replaces the reviewed files with accepted content. Use file proposal chooses the proposed conflicting values while retaining independent CareMap changes and validating the result. Invalid source still needs correction.

Both reviewed versions are kept in local recovery. If the files or accepted Guide changed since review opened, inspect the refreshed conflict before choosing again. A proposal for deleted content may require a new identity rather than restoring an old record.

Handle waiting work

Use Retry synchronization after restoring connectivity or correcting the reported problem. A held SDK batch still needs completion or release; retrying does not bypass its hold.

A late save to an older file can appear as a preserved proposal. Review this proposal brings it into conflict review rather than silently overwriting newer accepted content.

Project status and SDK replies can lag. A timeout alone does not prove the session ended or the change failed. Confirm the visible Guide or accepted source before reporting success or repeating a structural edit.

Recover a previous session

1. Reopen the eligible Guide in the desktop editor.
2. Open its project status details.
3. Under Previous session recovery, choose the dated entry.
4. Compare the preserved text with the current accepted files.
5. Copy the changes you still want into your editor, save, and review acceptance.

Recovery entries are proposals, not changes already reapplied. Reopening starts from the accepted Guide. For an old upload, use the separate Resume this media import action described in project media.

Recovery is local, retained for up to 30 days, with at most 20 sets per Guide. Preserve important work elsewhere before those limits are reached.

Closing the editor removes tracked CareMap working files while preserving your separate notes, scripts, and originals. If cleanup reports an error, keep the recovery material; CareMap retries its ownership cleanup when the project reopens.

If access was revoked, resolve the permission or workspace capability problem before reopening. Recovery does not grant authority to change the Guide.