No visibility into UUIDs for recurring meetings

Is there any way to know, for recurring meetings, the UUID of the next iteration? According to our tests the UUID is generated when the meeting starts and not in advance, so it limits our ability to identify meetings as well and plan them ahead of schedule.