Settings

Run and analyze

The most important Settings workflow for day-to-day use is Sync. Use it when files changed outside the UI, when entities look stale, or when generated artifacts and the database stopped agreeing.

Job to be done: recover from driftPrimary page: Settings -> SyncAdvanced alternative: CLI sync scripts

Open Troubleshooting Open Sync and Scripts

Workflow context

Do this

1. Open Settings -> Sync.
2. Review the pending-count badges to see which asset types are out of sync.
3. Run a specific tile when you know the affected area, or use Sync All when the drift is broad.
4. Let AppraiseJS run prerequisites in the correct order.
5. Re-open the page or affected entity list to confirm pending counts dropped.

The page should show users exactly where the recovery controls live before they assume they need scripts. Keep the screenshot anchored here so the visual confirmation appears at the same moment as the recovery steps.

Once that screen is available, users should be able to confirm success by watching the pending counts drop and then returning to the affected entities without leaving the UI flow.

Minimal example

• You pull a branch that changed locator files and test case artifacts.
• Locators and Test Cases show pending counts.
• Running Sync All resolves the prerequisite order automatically.

What good looks like

• Pending counts reflect real drift rather than staying stale.
• Entities appear consistently in the UI and generated files after sync.
• You only use CLI maintenance scripts when the UI is unavailable or automation requires it.

Next step

Use Test Runs or Reports once the project is back in sync.