[P2] Duplicate Error Notifications Displayed

[JoshuaAFerguson]

Severity: P2 - LOW (Cosmetic)
Component: UI - Notification System
Pages: My Applications, possibly others

Issue

Error messages displayed twice in notification toasts simultaneously.

Example: "Failed to create session" shown twice

Impact

• Poor UX
• Visual clutter
• Users see redundant error messages

Root Cause

Likely one of:

1. Error handler called twice (component + global handler)
2. Notification triggered in both API interceptor and component
3. Error bubbling through multiple layers

Files to Check

• ui/src/api/client.ts - Axios interceptors
• ui/src/hooks/useNotification.ts - Notification hook
• ui/src/pages/user/MyApplications.tsx - Component error handling

Fix Required

// BEFORE (likely causing duplicates):
try {
    await api.post('/sessions', data)
} catch (error) {
    showNotification(error.message, 'error') // Called here
    // AND also called in axios interceptor
}

// AFTER (only show once):
try {
    await api.post('/sessions', data)
} catch (error) {
    // Error already shown by axios interceptor
    // OR show here but disable interceptor notification
}

Fix Strategy

• Decide: Show errors in components OR in global interceptor, not both
• Add flag to prevent duplicate notifications
• Use notification deduplication (track recent messages)

Testing

• Error shown only once
• Multiple errors don't duplicate
• Success messages don't duplicate
• Error messages across all pages

Effort: 1-2 hours
Priority: Can defer to v2.1
Source: .claude/reports/UI_BUG_FIXES_REQUIRED.md

[JoshuaAFerguson]

Status: Deferred to v2.1 per UI_BUG_FIXES_REQUIRED.md

Priority: P2 (Low Priority)

Recommendation from bug report:

"Fix: Review notification trigger logic, add deduplication"
"Severity: Low - annoying but doesn't block functionality"

Decision: Per the comprehensive UI testing report, this is a UX polish issue rather than a blocking bug. Functionality works correctly but creates duplicate notifications.

Suggested Resolution:

1. Add notification deduplication logic in NotificationQueue component
2. Review notification trigger points to eliminate double-firing
3. Consider adding notification IDs for duplicate detection

Timeline: Deferred to v2.1 for UX polish phase

Branch: claude/v2-builder (no changes for this issue)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.

Action Required:

• If this issue is still relevant, please add a comment to keep it open
• If this is blocked, add the status:blocked label
• If this is no longer needed, it will be closed in 7 days

[github-actions]

This issue was automatically closed due to inactivity.

If you believe this was closed in error, please reopen it with a comment explaining why it should remain open.