# Handle a stale working copy

Refuse a proposal when another maintainer has already saved a newer version.

Source: https://help.smartfact.ai/configsheets/guides/configsheets-stale-version

Audience: Operator

Use an authorised SmartFACT account and synthetic practice data. This desktop guide follows the complimentary invited pilot. Background connections and Google Sheets synchronisation are outside its scope.

## Handle a stale working copy

1. **Open reference tables**

   Open reference tables.

   This exercise uses a separate table so it cannot alter the shared example.

2. **Open the concurrent edit example**

   Open the concurrent edit example.

   This is the real version-one page. The fixture now saves a separate, reviewed correction as another maintainer, leaving this screen with the old revision.

3. **Draft a change in the older page**

   Draft a change in the older page.

   The draft still refers to version one. Another maintainer has saved version two since the page was read.

4. **Review the stale proposal**

   Review the stale proposal.

   The server refuses the stale revision. Keep the draft, compare the current saved table in another tab, then reload and review a fresh proposal. Do not force an overwrite.

[Watch or practise this chapter](https://help.smartfact.ai/configsheets/demo?guide=configsheets-stale-version&chapter=stale-version&audience=office)

Keep receiving-product review and activation separate from saving or exporting reference data.