[futo-claudio]

Point Immich users rebuilding a machine at Restore From Backup on the welcome page instead of importing the key in the normal setup flow.

• main
  • docs: restore Immich onto a new instance from the welcome page #92 👈

[futo-kritika]

Confidence Score: 4/5

[Low risk] The review checked only the Immich restore flow's last steps (file restore, database backup selection, Restore confirmation) against PR 27817. It does not show that the earlier steps match: the Welcome page "Restore From Backup" wording, the "Where would you like to restore from?" prompt, the "Import recovery key" dialog, the claim that a post-admin import starts a fresh backup, and the "#1-switch-to-the-beta-build" anchor on the getting-started page. The risk is low because this is a …

Approved

Findings

Earlier findings (1 resolved)

• packages/docs/src/routes/guides/restore/+page.md:46 Include the final database restore confirmation · correctness · resolved

Summary

Documents Immich recovery through the welcome-page restore flow.

The recovery-key guide directs fresh Immich installations to Restore From Backup, while the restore guide separates Immich recovery from standalone recovery. The revised final step describes the latest-database selection and explicit Restore confirmation implemented in Immich's RestoreFlowAutoSelectBackup.svelte and handleRestoreDatabaseBackup.

Review context · 5 sources · 1/6 commands

• Sources:
  • https://redirect.github.com/immich-app/immich/pull/27817
  • https://redirect.github.com/immich-app/immich
  • https://redirect.github.com/immich-app/immich/blob/14ea2fd6d0da8bcf5f027a8f7a7230398ec17dbd/web/src/routes/maintenance/MaintenanceRestoreFlow.svelte
  • https://redirect.github.com/immich-app/immich/blob/14ea2fd6d0da8bcf5f027a8f7a7230398ec17dbd/web/src/routes/maintenance/RestoreFlowAutoSelectBackup.svelte
  • https://redirect.github.com/immich-app/immich/blob/14ea2fd6d0da8bcf5f027a8f7a7230398ec17dbd/web/src/lib/services/database-backups.service.ts
• Commands run: gh

_{Reviews (2) · Last reviewed commit: "docs: document the database restore conf..." · openai/gpt-6.1-sol · $0.18}

[futo-kritika]

Include the final database restore confirmation · correctness

When rebuilding a fresh Immich instance, confirming the snapshot only restores the files; it does not automatically restore the Immich database and restart as this step says. In the linked Immich feature branch, MaintenanceRestoreFlow.svelte routes the completion callback to RestoreFlowAutoSelectBackup.svelte, which requires clicking Continue and then confirming Restore through handleRestoreDatabaseBackup. A reader following these steps stops before the database restore and remains in maintenance mode. Document these final actions explicitly.

Suggested change

	6. Pick the backup, then the snapshot you want, and confirm. Once the files are back, Immich restores its database from them and restarts.
	6. Pick the backup, then the snapshot you want, and confirm. Wait for the files to finish restoring.
	7. On the database restore screen, review the selected database backup, or choose a different one. Select **Continue**, then confirm **Restore** to restore the database and restart Immich.

Prompt for a coding agent

In packages/docs/src/routes/guides/restore/+page.md, change the end of Immich step 6 and add a step describing the database restore screen after the file restore: review the automatically selected latest database backup (or select another), click Continue, and confirm Restore. Do not describe the database restore and restart as automatic after the snapshot restore.

[futo-claudio]

Confirmed: RestoreFlowAutoSelectBackup.svelte needs Continue and the handleRestoreDatabaseBackup confirm (Restore). Fixed in 09b257c with a step 7.

[github-actions]

Docs preview (09b257cd31c53029afdd8bac6f832695ef35a030)

https://pr-92.docs-futo-cloud-dev.pages.dev

[futo-kritika]

kritika: confidence 4/5 with low risk at 09b257c.