Daylite Integration

When using Daylite calendar integration, there are important limitations to consider, especially when working with external calendars and recurring events.
1. iCloud Integration & Busy/Free Status
While Daylite provides explicit Busy/Free statuses for its own events, there is a limitation when external calendars—such as iCloud—are involved (iCloud → Daylite → SimplyMeet.me).

iCloud events that appear in Daylite are synced via Apple’s EventKit framework. This means they are only locally mirrored in Daylite and are not actually stored within the system.

Because of this:

• Busy/Free statuses from iCloud events may not be correctly passed through Daylite to SimplyMeet
• These events may not block availability in external booking systems

To resolve this issue, please connect your external calendars directly to your SimplyMeet account, bypassing Daylite as an intermediary.

2. Recurring Events & Busy Status
Currently, recurring events are not supported by the Daylite API.
While the initial (base) event of a recurring series may be accessible, the individual recurring instances and their details are not returned through the API.
As a result:

• Recurring appointments may not be fully recognized by external systems
• Their Busy status may not be applied correctly for availability or conflict checks
  

These limitations should be taken into account when configuring calendar integrations and availability rules.