Bug Report: Multiple inbox/session requests being performed which then return 429

[josedias-np]

📜 Description

The Novu SaaS dashboard performs several 'https://api.novu.co/v1/inbox/session' requests, which then return a 429 code.
This issue is also observed within our own web platform, particularly when our front-end application makes multiple requests to our own APIs.
For each request that's performed on our side, a /inbox/session request is performed by Novu that endup returning:
message : "API rate limit exceeded" path : "/v1/inbox/session" statusCode : 429 timestamp : "2025-12-22T12:50:58.921Z"

👟 Reproduction steps

1. Access the Novu SaaS dashboard;
2. Perform several actions in a short span of time that will trigger multiple requests.

👍 Expected behavior

There shouldn't be so many /inbox/session requests being made.

👎 Actual Behavior with Screenshots

A /inbox/session request is performed for each internal request that's made by our front-end application.

Novu version

Novu SaaS

npm version

No response

node version

No response

📃 Provide any additional context for the Bug.

No response

👀 Have you spent some time to check if this bug has been raised before?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to submit PR?

None

[linear]

NV-7000

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• 🐛 Bug Report: Api v2.2.0 Self-Hosted: /api/v1/notifications > 24 h throws "date range exceeds your plan's retention period" #8528
• 🐛 Bug Report: More actions button #8895
• 🐛 Bug Report: HTTP 500 error on all /v1/notifications GET requests #8789
• 🐛 Bug Report: Novu not working properly in the docker/community docker compose file. #9300
• 🐛 Bug Report: Self‑hosted API 2.1.1 rejects /v1/inbox/session body sent by @novu/nextjs 3.2.x #8239

👤 Suggested Assignees

• FilipSwiatczak
• sanirasheed
• joshdk
• Harmeet10000
• paul-github-1

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[scopsy]

Hi @josedias-np thank you for reporting this! In our case we had un-necessery remounting of the component passing a new subscriber object instance for each re-render fixed here: #9728

In your particular scenario, do you have an example of a snippet of your instance component initiation?