[BUG] Trezu - Requests: Notification link after request deletion redirects to invalid page

[rknearn-qa]

Summary

When a pending request is deleted, a notification appears containing a link. Tapping this link redirects the user to a Requests page URL that does not represent a valid or existing state, resulting in unnecessary or incorrect navigation.

Preconditions:

• A pending request exists
• User has permission to delete the request

Steps To Reproduce

1. Delete a pending request
2. Tap the notification link that appears after deletion
3. Observe the redirect behavior

Actual Result:

• User is redirected to:

  https://trezu.app/romakqatesting.sputnik-dao.near/requests

• Redirected page does not reflect a valid or relevant state related to the deleted request

• An unnecessary or incorrect request link is generated

Remove.Request.webm

Expected Result:

• Notification link should:

  • Redirect to a valid and existing resource
  • OR not be displayed if the request no longer exists
  • OR redirect to a contextual fallback page (e.g., general Requests list with proper state handling)

Special Notes:

Possible Root Cause:

* Notification system generates redirect URL based on request metadata without validating request existence after deletion
* Missing conditional logic to prevent link generation for deleted entities
* Stale state reference in frontend notification handler

Workarounds:

• Manually navigate back to the correct Requests page

Repro Rate:

Always

Setup - OS - Browser - Environment

• OS / Devices: Windows 11 (x64), Motorola G23 (Android 14), Iphone XR (iOs)
• Screen resolution(s): 1366 x 768, 1600 x 720, 1792×828
• Browser(s) + version(s): Chrome (144.0.7559.97), Mozilla Firefox (147.0.2), Brave (1.86.148)
• Wallet: Meteor
• App environment: Staging (trezu.app)
• Near Network: Mainnet

Resources & Additional Notes

Impact:

User Impact:

• Confusing navigation after request deletion
• Users may assume deletion failed or that a ghost request exists

System Impact:

• Incorrect routing behavior
• Potential inconsistency between UI notifications and actual data state

Business / Release Risk:

• Minor UX degradation
• Increased support questions related to “missing” or “ghost” requests

QA Verdict:

Verdict: ❌ Needs Fix
Rationale:

• Notifications must accurately reflect system state
• Redirecting to invalid or irrelevant pages undermines user trust in workflow consistency

Recommendation:

• Validate entity existence before generating notification link
• Implement fallback routing when resource no longer exists
• Add regression test for deletion → notification → redirect flow

Priority

🟡 P2 : Medium