You made a change to a recurring event of your Event or Event v2 Feature, but you noticed that this change will not show on the app, even though it shows on the CMS Dashboard.
This article explains why making a change may not reflect on the app and how you can work around it.
As per the platform design, when you make changes to existing recurring events, those changes will only apply to new occurrences, meaning you will need to individually change each occurrence that has already been generated within the CMS.
If you are not interested in past events, apart from just having the change apply to the upcoming events, you can also create a new set of recurring events incorporating the change you wish and delete the old set. This may be useful if you wish to have a 'clean start' and don't mind erasing the old events. This way you will not be having events of the same set with different options.
Nonetheless, if you wish to have this change applied to the already generated events from a specific 'recurring events' set (ie past events created before the date you made the change), you will need to individually change each occurrence that has already generated within the CMS.
For more information please refer to the KB articles under the Related Articles Section
If you decided to individually change each occurrence that has already been generated within the CMS before the date of the change, this change you made will show for these occurrences on the app, too.