# Uncaught (in promise) error

**URL:** https://meta.discourse.org/t/uncaught-in-promise-error/385342
**Category:** Bug
**Tags:** events, needs-repro
**Created:** [October 11, 2025, 9:36pm UTC](https://meta.discourse.org/t/uncaught-in-promise-error/385342 "2025-10-11T21:36:15Z")
**Posts on this page:** 1
**Showing post:** 24

<div class="post-metadata">

### Author: ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)
#### Post date: [March 22, 2026, 7:34am UTC](https://meta.discourse.org/t/uncaught-in-promise-error/385342/24 "2026-03-22T07:34:49Z")

</div>

Update (March 2026):

The behaviour described in the OP seems to have changed. I’m no longer seeing the rate-limited loading behaviour in the FullCalendar view.

However, I am now experiencing rate limiting when accessing the new `/discourse-post-event/events.ics` export endpoint instead.

This appears to affect external calendar subscriptions rather than the internal FullCalendar UI.

---

_[View the full topic](https://meta.discourse.org/t/uncaught-in-promise-error/385342)._