Back to Signal Feed
CodeTracked since May 19, 2026

Graceful recovery when navigating back to a deleted conversation

Fixes ELECTRON-19G by handling deleted-conversation 404 responses in the conversation fetch flow, so the app no longer rethrows an unhandled rejection on a stale `/conversation/<id>` route and instead recovers with a not-found warning and redirect to home.

ConversationIndexConversationArtifactProvideruseNavigationTypeBackendHttpError

What Happened

  • Fixes ELECTRON-19G by handling deleted-conversation 404 responses in the conversation fetch flow, so the app no longer rethrows an unhandled rejection on a stale `/conversation/<id>` route and instead recovers with a not-found warning and redirect to home.
  • Fixes ELECTRON-19G by handling deleted-conversation 404 responses in the conversation fetch flow, so the app no longer rethrows an unhandled rejection on a stale `/conversation/<id>` route and instead recovers with a not-found warning and redirect to home.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Introduced a recoverable missing-conversation path: the conversation fetcher now catches `BackendHttpError` 404s from `ConversationIndex`/`ConversationArtifactProvider` flows, displays the new `conversation.notFound` warning, and navigates with `replace: true` via navigation history handling so back-button navigation cannot loop to the deleted conversation route.

Why Track This

Why It Matters

For users who delete chats and immediately navigate with the back button, the app now returns to the welcome page instead of leaving them in an empty conversation shell or triggering an unhandled promise rejection, so workflow continuity is restored and support noise from repeated 404 navigation crashes should drop. The underlying mechanism uses `ConversationIndex` error swallowing plus `useNavigationType()` history replacement; teams should continue watching for other conversation routes that still allow stale `#/conversation/<id>` entries to trigger unhandled 404 rethrows or back-stack inconsistencies.

Impact

For users who delete chats and immediately navigate with the back button, the app now returns to the welcome page instead of leaving them in an empty conversation shell or triggering an unhandled promise rejection, so workflow continuity is restored and support noise from repeated 404 navigation crashes should drop. The underlying mechanism uses `ConversationIndex` error swallowing plus `useNavigationType()` history replacement; teams should continue watching for other conversation routes that still allow stale `#/conversation/<id>` entries to trigger unhandled 404 rethrows or back-stack inconsistencies.

What To Watch Next

  • Watch whether ConversationIndex becomes a repeated pattern.
  • Track follow-up changes around AI IDE.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: other_conversation_routes_still_throwing_unhandled_404s, back_stack_regression_after_replace_navigation.
Open Topic TimelineOpen Technical EventOpen Original Sourceother_conversation_routes_still_throwing_unhandled_404s / back_stack_regression_after_replace_navigation / missing_i18n_conversation_notfound_key_in_locale_overlays

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

iOfficeAI/AionUi PR #2936: fix(chat): redirect to home when conversation is missing

In the repro flow, opening conversation A then deleting it and pressing Back from conversation B used to stay on `#/conversation/<deletedId>` with 404s; after this change it shows a `conversation.notFound` toast and lands on `/` with back navigation disabled for that jump.