[Bug] Fix Duplicate Toast Notifications After Retry

[Abd-Standard]

Description

Users occasionally receive multiple success toasts after retrying failed notifications. Investigate and resolve the duplicate rendering issue.

Tasks
Reproduce the bug.
Identify duplicate trigger source.
Implement fix.
Add regression test.

Acceptance Criteria
Only one success toast is displayed.
Retry flow remains functional.
Regression test passes.

[nelly439]

Hi, I’d like to take this on.

I understand the issue is duplicate success toasts during the retry flow, likely caused by multiple trigger points or repeated state updates. I’ll start by reproducing the bug, trace the source of duplicate emissions, and implement a fix to ensure only a single toast is shown without breaking the retry logic.

I’ll also add a regression test to cover this scenario and prevent future occurrences.

Let me know if I can proceed.

[Chrisbankz0]

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript and more

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

[Chrisbankz0]

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript and more

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

[Chrisbankz0]

Hello, I’m a full stack developer with hands-on experience building with variety of tools including Nextjs, nodejs, nestjs, React, Typescript and more

I focus on writing clear, maintainable code and making sure features work as expected end to end, not just in isolation. I communicate progress regularly and keep things transparent as I work. I’m confident I can complete this task within an ETA of 4 HOURS

[barry01-hash]

https://contribute.grantfox.xyz/org/Core-Foundry/repo/Notify-Chain/issue/89

[Chigybillionz]

Hi, I'd like to work on this issue.

I'm a full-stack developer comfortable debugging React state and event handling. My plan:

• Reproduce the bug by triggering a failed notification retry
• Trace the duplicate toast to its source (likely a toast call firing in multiple places or an effect running more than once)
• Fix the root cause and add a regression test confirming only one toast appears per retry

Can I be assigned?

[mxrtins04]

I've debugged duplicate toast issues before they almost always come from either multiple event listeners accumulating on retry (listener not cleaned up between attempts), a state update triggering re-renders that fire the toast effect more than once, or the retry handler being called twice due to a missing debounce or double-click guard. My approach is to first reproduce reliably by instrumenting the toast trigger with a call counter, then trace the retry flow to find exactly where the duplicate dispatch originates. Once the source is identified, the fix will be targeted: remove the stale listener, stabilize the effect dependency array, or add a ref-based guard on the handler depending on what the trace shows. I'll add a regression test that simulates a failed notification, retries it, and asserts the toast fires exactly once.

[grantfox-oss]

🦊 GrantFox — @barry01-hash has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #86)
2. Your PR will be reviewed by the Core-Foundry maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@barry01-hash's PR #91 was approved and merged by @Abd-Standard.

🏆 @barry01-hash: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (258 total points). Track your full progress on GrantFox.

👏 Great work, @barry01-hash! Keep contributing to Core-Foundry.