Strixa AI
TopicsSearchPricing
Sign inStart tracking

Signal Detail

Loading signal detail

Reading this signal card's judgment, risks, and evidence.

Strixa AI
TopicsSearchPricing
Sign inStart tracking
Back to Signal Feed
CodeTracked since May 19, 2026

Prevent broken back-navigation after deleted conversation by showing not-found toast and replacing to home

AionUi PR #2936 changes conversation navigation so that a deleted conversation ID returning 404 is handled in the fetcher instead of bubbling as an unhandled rejection, shows a single `conversation.notFound` warning toast, and redirects users to the home page using history replace so the stale route is not re-entered.

ConversationIndexNavigationHistoryContextuseNavigationTypenavigate('/', { replace: true })

Signal Intelligence

Confidence Level95%
Worth Continued TrackingFinal score 81% with 1 evidence item.
Primary Impact Areas
ConversationIndexNavigationHistoryContextuseNavigationType

What Happened

  • AionUi PR #2936 changes conversation navigation so that a deleted conversation ID returning 404 is handled in the fetcher instead of bubbling as an unhandled rejection, shows a single `conversation.notFound` warning toast, and redirects users to the home page using history replace so the stale route is not re-entered.
  • AionUi PR #2936 changes conversation navigation so that a deleted conversation ID returning 404 is handled in the fetcher instead of bubbling as an unhandled rejection, shows a single `conversation.notFound` warning toast, and redirects users to the home page using history replace so the stale route is not re-entered.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Added concrete missing-conversation handling in the Conversation index fetch path, converting an unhandled BackendHttpError into a controlled not-found warning and safe redirect, while updating history rewrite logic so back navigation no longer returns users to the deleted conversation URL.

Why Track This

Why It Matters

Desktop users who delete a conversation and then navigate back no longer get stuck on a dead conversation page with repeated 404 failures; they now land on the welcome screen with a clear notice, which directly improves recoverability of everyday navigation flows and reduces crash-like support incidents. The fix works by catching the conversation fetch failure in `ConversationIndex`, preventing SWR from re-throwing it as an unhandled promise rejection, and using `replace: true` navigation plus `NavigationHistoryContext` cursor rewriting to keep the invalid route out of history; next, monitor whether other 404 conversation paths still leak to Sentry (especially ELECTRON-19G) and whether any legitimate back-navigation behavior regresses after the replace-based redirect.

Impact

Desktop users who delete a conversation and then navigate back no longer get stuck on a dead conversation page with repeated 404 failures; they now land on the welcome screen with a clear notice, which directly improves recoverability of everyday navigation flows and reduces crash-like support incidents. The fix works by catching the conversation fetch failure in `ConversationIndex`, preventing SWR from re-throwing it as an unhandled promise rejection, and using `replace: true` navigation plus `NavigationHistoryContext` cursor rewriting to keep the invalid route out of history; next, monitor whether other 404 conversation paths still leak to Sentry (especially ELECTRON-19G) and whether any legitimate back-navigation behavior regresses after the replace-based redirect.

What To Watch Next

  • Watch whether ConversationIndex becomes a repeated pattern.
  • Track follow-up changes around AI Debugging and Error Localization.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: back_button_still_navigates_to_deleted_conversation, sentry_19g_events_not_declining.
Open Topic TimelineOpen Technical EventOpen Original Sourceback_button_still_navigates_to_deleted_conversation / sentry_19g_events_not_declining / unhandled_errors_in_other_conversation_routes

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

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

Repro: open A, delete A, open B, press back repeatedly until route would return to deleted A; previously SWR re-threw 404s and left `#/conversation/<deletedId>` active.