# 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:** 25

<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:47am UTC](https://meta.discourse.org/t/uncaught-in-promise-error/385342/25 "2026-03-22T07:47:34Z")

</div>

I was able to successfully subscribe to the calendar in Moodle by:  
1. Changing the URL scheme from `https://` to `webcal://`  
2. Adding `&after=DD-MM-YYYY` to the query string

This effectively reduces the number of exported events and prevents the rate limiting.

> [@Re-add full ics export](https://meta.discourse.org/t/re-add-full-ics-export/230713/9):
>
> If your site has more events than that and you want to do a full export, you may iterate through by using the `before` and `after` query parameters which accept date strings.

This confirms the endpoint supports date-windowed exports, and using `?after=DATE` for subscriptions is an effective way to keep the ICS feed lightweight and scalable, even if the forum has many historical events. Combining `webcal://` with `?after=DATE` gives an ideal setup for external calendar clients: only future events, small ICS file, and stable performance.

---

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