<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://help.simplymeet.me/index.php?action=history&amp;feed=atom&amp;title=Daylite_Integration</id>
	<title>Daylite Integration - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://help.simplymeet.me/index.php?action=history&amp;feed=atom&amp;title=Daylite_Integration"/>
	<link rel="alternate" type="text/html" href="https://help.simplymeet.me/index.php?title=Daylite_Integration&amp;action=history"/>
	<updated>2026-06-10T15:23:29Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://help.simplymeet.me/index.php?title=Daylite_Integration&amp;diff=8840&amp;oldid=prev</id>
		<title>Admin: Created page with &quot;When using Daylite calendar integration, there are important limitations to consider, especially when working with external calendars and recurring events. &lt;br&gt; &#039;&#039;&#039;1. iCloud Integration &amp; Busy/Free Status&#039;&#039;&#039;&lt;br&gt; While Daylite provides explicit &#039;&#039;&#039;Busy/Free statuses&#039;&#039;&#039; for its own events, there is a limitation when external calendars—such as iCloud—are involved (iCloud → Daylite → SimplyMeet.me).&lt;br&gt;  iCloud events that appear in Daylite are synced via Apple’s E...&quot;</title>
		<link rel="alternate" type="text/html" href="https://help.simplymeet.me/index.php?title=Daylite_Integration&amp;diff=8840&amp;oldid=prev"/>
		<updated>2026-05-12T11:44:35Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;When using Daylite calendar integration, there are important limitations to consider, especially when working with external calendars and recurring events. &amp;lt;br&amp;gt; &amp;#039;&amp;#039;&amp;#039;1. iCloud Integration &amp;amp; Busy/Free Status&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt; While Daylite provides explicit &amp;#039;&amp;#039;&amp;#039;Busy/Free statuses&amp;#039;&amp;#039;&amp;#039; for its own events, there is a limitation when external calendars—such as iCloud—are involved (iCloud → Daylite → SimplyMeet.me).&amp;lt;br&amp;gt;  iCloud events that appear in Daylite are synced via Apple’s E...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;When using Daylite calendar integration, there are important limitations to consider, especially when working with external calendars and recurring events.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;1. iCloud Integration &amp;amp; Busy/Free Status&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
While Daylite provides explicit &amp;#039;&amp;#039;&amp;#039;Busy/Free statuses&amp;#039;&amp;#039;&amp;#039; for its own events, there is a limitation when external calendars—such as iCloud—are involved (iCloud → Daylite → SimplyMeet.me).&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
iCloud events that appear in Daylite are synced via Apple’s EventKit framework. This means they are only &amp;#039;&amp;#039;&amp;#039;locally mirrored&amp;#039;&amp;#039;&amp;#039; in Daylite and are not actually stored within the system.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Because of this:&amp;lt;br&amp;gt;&lt;br /&gt;
* Busy/Free statuses from iCloud events may not be correctly passed through Daylite to SimplyMeet&lt;br /&gt;
* These events may not block availability in external booking systems&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
To resolve this issue, please connect your external calendars directly to your SimplyMeet account, bypassing Daylite as an intermediary.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;2. Recurring Events &amp;amp; Busy Status&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
Currently, &amp;#039;&amp;#039;&amp;#039;recurring events are not supported by the Daylite API.&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
While the initial (base) event of a recurring series may be accessible, the individual recurring instances and their details are &amp;#039;&amp;#039;&amp;#039;not returned through the API.&amp;#039;&amp;#039;&amp;#039;&amp;lt;br&amp;gt;&lt;br /&gt;
As a result:&lt;br /&gt;
* Recurring appointments may not be fully recognized by external systems&lt;br /&gt;
* Their Busy status may not be applied correctly for availability or conflict checks&amp;lt;br&amp;gt;&lt;br /&gt;
These limitations should be taken into account when configuring calendar integrations and availability rules.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
</feed>