Skip to content

News

Update

Improvements

  • When using Microsoft Exchange Server, ChronoLink now also synchronizes the visibility and status fields.

    • When synchronizing to Outlook.com or Exchange Online, the values for both fields will be kept. When the target is a Google calendar, ChronoLink will translate the values to their closest equivalent. For details, see the "Status" and "Visibility" tables in our docs.
    • Use the status and visibility conditions to select which events to (not) synchronize, and alter the field values using the statuschange and visibilitychange transformers.

    Setup

    Existing users need to install version 1.1.0 of ChronoLink Connector for Outlook. The installer will upgrade the existing installation.

    For general setup instructions, read the "Exchange Server" page of our user guide.

Fixes

  • Reverted most of the update interval change for iCalendar (ICS) feeds.
    • It turns out that most feeds used by our beta testers set the update interval way too high. For example, having a feed about table reservations only update once per day defeats the purpose of having the feed in the first place.
    • As a quick fix, we reverted our iCalendar code to the old behavior for all feeds except those by Facebook.
    • We plan to introduce a connection-level setting for this in the future.

Update

Improvements

  • When reading events from iCalendar (ICS) feeds, ChronoLink now respects minimum update intervals suggested by the feed.

    • Previously, ChronoLink tried to fetch feeds every three minutes, which is the same interval it uses for Google Calendar, Outlook.com / Exchange Online and other sources.
    • With this change, we fix a problem with Facebook "upcoming events" feeds: after a few hours with the interval mentioned above, the Facebook servers would refuse requests for that feed for about 24 hours or more! Respecting the update interval they suggest in the feed (12 hours) solves this problem.
    • Note that you can always manually trigger a connection run regardless of when the next one is scheduled to occur.

    Finding the update interval

    Enter the address of the feed in a browser to view it, or download it and open it in a text editor.

    Search for a line starting with X-PUBLISHED-TTL. The value at the end of the line should look something like PT12H (12 hours), P2D (2 days) or P1W (1 week).

    If you can't find such a line, the update interval is unspecified and ChronoLink uses its default schedule.

Update

Improvements

  • ChronoLink can now read calendars from Microsoft Exchange Server in addition to the existing support for Outlook.com and Exchange Online.
    • By installing our connector software for Microsoft Outlook, you can enable ChronoLink to seamlessly and securely access all calendars in your Exchange account.
    • This release covers basic event data: title, description, location, event type (meeting or non-meeting).
    • In future releases, we plan to cover more data (status, visibility). We will also add support for writing to Exchange calendars.
    • Detailed setup instructions can be found on the "Exchange Server" page of our user guide.

Update

Improvements

  • Synchronization connections now support limiting past events, future events or both to "today only".
    • Previously, the shortest time for both settings was "2 weeks back" and "2 weeks ahead", respectively.

Website Update

  • Our news blog, which was previously hosted by Headway, has now been integrated into the main ChronoLink website.

Update

Improvements

  • ChronoLink now supports event reminders for Google and Microsoft.
    • Add the reminderset transformer to your connection configuration to use this feature. The new Reminders section of our User Guide has additional information.
  • Added ability to write "Out of Office" events to Google Calendar. This makes it possible to seamlessly synchronize vacations, holidays etc. with Microsoft calendars ("Show as: Away") in both directions.
    • To turn a regular event into an Out of Office event, add the statuschange transformer to your connection configuration.
    • Previously, Google did not offer a way for third-party applications to write such events; they could only be read. Recently, however, Google extended their API to cover this.

Update

Improvements

  • Google Calendar connections that fail for the reasons listed below are now marked as broken, displayed with an explosion icon (💥) and not retried until triggered manually.
    • ChronoLink permissions were revoked using Google's account settings page:
      To resume synchronization, log in to my.chronolink.app, then click the 🔄 icon for the respective linked account to re-authorize ChronoLink.
    • An organization administrator deleted your Google Workspace account:
      The deleted account prevents the ChronoLink settings page from working properly. Please contact ChronoLink support so we can unlink the Google Workspace account to restore ChronoLink functionality for your remaining accounts.

Update

Improvements

  • To create a ChronoLink account, new users now have to click one of the Sign up using Google or Sign up using Microsoft buttons. Also, ChronoLink now displays a success message after an account was created.
    • Previously, there were no separate "Sign up" buttons. When logging in using a new Google/Microsoft account, a new ChronoLink account was created automatically without asking or notifying the user.
  • When you add a linked account or add calendar access, ChronoLink now displays a success message on top of the settings page. Previously, it only silently jumped back to that page.

Update

Improvements