Uncaught (in promise) error

Bug
1

Description

After a recent Discourse rebuild (self-hosted), I am consistently encountering user-facing rate limiting when viewing the main Full Calendar Version 6, even though my site has very low activity (1–2 simultaneous users). This behavior started appearing after my last two rebuilds.

My rate limit configuration (as set in app.yml):

  • DISCOURSE_MAX_ADMIN_API_REQS_PER_MINUTE: 4x default
  • DISCOURSE_MAX_REQS_PER_MINUTE: 4x default
  • DISCOURSE_MAX_REQS_PER_DAY: 4x default
  • No per-IP rate limit is specified.

Observations

  • No errors are shown in /logs.
  • No reverse proxy is in use (standard Let’s Encrypt container and an A record on domain).
  • Only calendar views seem to trigger this unexpected rate limiting.
  • There have been no changes to user activity
  • all plugins and theme components are official
  • This started only after a recent Discourse rebuild. Continued after tonight’s rebuild
  • Admin > Logs are clean at time of incident.

Troubleshooting so far

  • Confirmed the custom rate-limit settings are present and well above defaults.
  • Tried multiple browsers, cleared caches.
  • meta.discourse.org topics suggest there may be additional undocumented internal rate limits overriding custom values after upgrades.

References

Request

Could you please:

  1. Confirm if there are any new or hidden rate limiters that would affect background or plugin-generated requests after a recent update/rebuild, and if so, describe how to override or tune them.
  2. Advise why my high custom rate limits are not being respected for the calendar view.
  3. Suggest further troubleshooting or configuration changes, if any.

Thank you!

2

It looks like this could be related to Re-add full ics export - #9 by kelv because 100 events seem to show, then after about 2 minutes can display another large batch, and they don’t appear gradually but in large chunks.

Edit: This rate-limited behaviour is manageable for now, but becomes apparent when advancing far; i can see all the events for my current week and all the events in the next, it’s if i then proceed to the next week i hit the hard limit.

3

I should also clarify that, the upcoming events full calendar v6 wasn’t rate limited to this extent, before i set the custom api throttle settings. These app.yml settings didn’t change the rate limiting visible on FullCalendar :wink:

4

@kelv could you look at this please?

8

i can still repro this

9

We can’t repro this at all at the moment. Which commit are you on? How many events do you have?

10

Discourse latest-release +369

Docker_manager 3e5ec72d

Bbcode 633030d8

Categories suppressed d5550658

Who’s online 3fe319b8

Themes and Components

Default

[Category Banners]

Show banners on category pages using your existing category details. Learn more

[Clickable Topic]

If you want to edit this theme, you must submit a change on its repository

[Custom Header Links (icons)]

If you want to edit this theme, you must submit a change on its repository

[Discourse Gifs]

If you want to edit this theme, you must submit a change on its repository

[Inline PDF Previews]

If you want to edit this theme, you must submit a change on its repository

[Reader Mode]

If you want to edit this theme, you must submit a change on its repository

44 next Week

none of the ~40 loading Week after

11

FullCalendar had started behaving itself, because i went back a few weeks and then went forward many weeks

12

many, i think MAX_RESULTS has suppased its limit now after 27th September. I have to refresh Full Calendar to view my events each time i look

13

Im sorry but I fail to follow you. Are you able to make a video of you navigating the calendar please?

1 Like
14

on a PWA

1 Like
15

So where is the 429?

16

i don’t think it’s that kind of rate limit. When i mentioned API throttle settings, i really meant my Discourse is configured to handle many event topics, but FullCalendar view is not working as well as it used to before the code was merged

Apologies for the confusion

Edit: i have edited the OP to reflect the lack of 429 errors

17

18

I am on the latest versions. From a UI perspective, this problem fixed itself overnight. I updated last night but problem didn’t fix itself immediately. The total number of events that have passed is about 270. I have now changed back to using PWA…

19

my Discourse instance is up to date with tests-passed. I had a report from a seperate user of my instance yesterday that a future week view wasn’t loading all the events. Having already noticed that this error ceased to affect UI of the Current week view, i tried to pinpoint the error on my Laptop. Below is the video re-production;

the same “lack of events” in a future week, can be re-produced the same on my Smartphone

20

I’ve rebuilt and this issue continues to appear when moving from current week to the next week.

Were we able to diagnose what started to cause this?

perhaps i need to add a

somewhere in my app.yml

21

Update of Discourse by last 20 commits has fixed this bug

22

Haven’t updated, but this Bug has started happening again

Edit: went back into PWA and the bug isn’t happening

Edit2: still getting the error on my browser console on Laptop, didn’t check the calendar though