Rate limit triggered by rapid week navigation in Upcoming Events calendar

Contribute Bug
1

I am creating a new topic because I have now captured a definite HTTP 429 response with the error code user_10_secs_limit. My earlier report did not contain a confirmed 429 and was later considered resolved.

I tested moving rapidly through several consecutive weeks in the Upcoming Events calendar. After doing this, I checked the Firefox console and found request errors.

Tested page:

/upcoming-events/week/2026/7/13

Installed version

  • Discourse 2026.7.0-latest +314
  • Git commit cf0d9228b4
  • Ember v6.10.1

Steps to reproduce

  1. Open the Upcoming Events calendar in week view.
  2. Move forwards or backwards through multiple weeks in quick succession.
  3. Open the Firefox developer console.

Request error

Requests to /discourse-post-event/events begin returning HTTP 429 responses:

Slow down, you're making too many requests. Please retry again in 1 seconds. Error code: user_10_secs_limit.

The console logs the failed request from index.js:631:21.

Should the calendar debounce, cancel, or otherwise handle rapid navigation so that its event requests do not trigger the normal per-user request limit?

2

I also checked the host resource usage around the time of reproduction.

Over the surrounding hour, the 4-vCPU server averaged:

  • 96.45% CPU idle
  • load average 0.22
  • 1.28% disk utilisation
  • approximately 1.4 GB RAM still available

There were no blocked processes, meaningful I/O wait, or network saturation.

This therefore appears to be an application-level request limit rather than the server protecting itself because of CPU, memory, disk, or network pressure.