hi @Paul-Winterhalder.

Following up on our previous discussion, I have an additional question regarding leaderboard scheduling.

When we modify the Leaderboard Config to change the reset time, could you provide a way to apply those changes to already instanced/active division instances?

Currently, our service operates on a weekly tournament rotation. There are scenarios where we need to adjust the reset time of an ongoing tournament to a specific time based on certain triggers.

We’ve noticed that when we update the reset time via Design > Leaderboard Config:

For future divisions (those not yet created), the new "Calculate Result" time is correctly applied when they are eventually instanced.

For active divisions (those already instanced), the updated schedule is not reflected, and they continue to follow the old reset time.

For our service logic, it is critical that all divisions remain synchronized, ensuring they all start and end at the exact same time.

Is there a feature, an API, or a workaround to forcibly update the reset/rotation schedule for leaderboard instances that are already in progress?

Agreed @armitage - the bulk messaging feature is planned for the use case you describe... (and yup - still coming 🙂 ).

Yes, the link provided in that article is automatically updated. For your reference, here is the actual embedded link behind it:
https://portalx.braincloudservers.com/dts/cloudcode_dts_files.zip

brainCloud developers have just release several playable builds of our famous examples! See our cool features in action. Find them at https://getbraincloud.com/demos for Windows, Mac, online and mobile.