Skip to content

News

Update

Fixes

  • Fixed a bug that caused connections to fail when attempting to write an event with a non-empty "location" field to a Microsoft calendar.
  • Connections that involve a Microsoft calendar no longer fail if there are more than 1000 events in a single month.

Update

Fixes

  • Connections using Microsoft calendars as sink and/or source no longer fail randomly with Microsoft Graph returning the cryptic error code "UnknownError" to ChronoLink. Working with several beta testers and a developer support engineer from Microsoft, we were able to pinpoint and then fix the issue.
  • Fixed a bug that sometimes resulted in connection runs being queued for hours without getting their turn.

Improvements

  • Minor UI improvements on the configuration page. If you don't see them, clear your browser cache!
    • Connections that failed their last run now use ⚠️ as a status icon instead of the ambiguous ⚡.
    • As the "Automatic" trigger is not implemented in the backend yet, the corresponding checkbox was removed for now to avoid confusion.
    • Streamline the UI by replacing the term "Short ID" with "ID". Most users will only ever encounter short IDs, so the old term could cause confusion.

Update

Fixes

  • Due to several problems with connecting and using Microsoft accounts (Outlook.com / Exchange Online), we rewrote the auth token handling to use the same reliable mechanism ChronoLink uses for Google accounts.

To migrate and reactivate your settings, follow these steps: 1. Log in once using each of the Microsoft logins you have in your ChronoLink account. 2. For each Microsoft access, click the refresh (🔁) button, then select the correct account and re-authorize ChronoLink.

If you don't see those refresh buttons, clear your browser cache or reload the page by pressing Ctrl F5.

⚠️ Warning: Do not delete the Microsoft access. This would delete all associated connections.

Notes

  • As a side effect of recent changes, the UI will show the Add access to 'example@gmail.com' buttons for Google accounts even if you already added that access. Clicking the button and re-authorizing ChronoLink will update our records and make the button go away.
    • Note that this is harmless and does not affect other functionality.

Update

Improvements

  • When you create new connections or alter the conditions/transformers of an existing one, ChronoLink must perform full synchronization. For some connections, those with thousands of events, this can take a while. Previously, this connection run had to be completed before any other connection could run. Now, ChronoLink pauses such long-running connections at regular intervals, giving other connections a chance to run as well.

    • Such connections are displayed with a percentage value in the "Status" column instead of the usual "✔️".
    • Pausing and resuming are fully automatic. Sooner or later, each connection will complete the synchronization process.

  • For each connection, ChronoLink now displays the total number of events synchronized.

  • ChronoLink now synchronizes the Location field when both source and sink support it (Google and Microsoft calendars).

    • To suppress this, add the following transformer:

      {
    "type": "clear",
    "field": "LOCATION"
}

    • The location field can be used with all text-based transformers: overwrite, prepend, append and, as shown above, with clear.

    • The text condition now also supports "scope": "LOCATION".
      Note that if you did not specify scope or specified its default value ANY, your condition might match different events now because ChronoLink also searches the location field.

Update

Improvements

  • For Google accounts, multiple sync connections can now write to the same calendar independently. Previously, each such connection would delete the events written by the other one(s).
    • The limitation is still in place with Microsoft accounts. However, it will be lifted soon, as well.

Housekeeping

  • Due to enhancements in ChronoLink's rate limiting logic, connections using Google sources and/or sinks will now run quicker.

Update

Fixes

  • Fixed a bug that broke connections reading Google events with unusual Google Meet conference data. The affected connections will be retried automatically.

Update

Fixes

  • Fixed a bug that caused manually triggered connections to run repeatedly instead of once.

Housekeeping

  • Scheduled connections in state "failed" are now also retried once whenever the ChronoLink service is restarted or updated. Previously, they were only retried when you edited and saved them (even without making real changes).

Update

Improvements

  • The user interface now displays an error message when authorization for a linked account is invalid or expired. The message includes the ID of the access so you know which one to renew to fix the problem.

Housekeeping

  • Fixed a bug that slowed down the user interface significantly when an account had linked Google accounts.
  • Fixed a memory leak that caused failing connections and required regular service restarts.

Update

Improvements

  • In addition to GMail and Google Workspace accounts, ChronoLink now supports Microsoft accounts (Outlook / Office 365) both for logging in and for reading/writing calendar events.
  • ChronoLink now supports a status condition to check whether an event is marked as free/busy etc. Using the new statusset transformer, you can also change this value. See the reference for details.

Changes

  • Out of office events no longer have their own type. Instead of checking eventtype for AWAY, from now on you have to check status for OUT_OF_OFFICE (see above).

Update

Improvements

  • ChronoLink now supports a time condition for checking whether events are on certain days of week and/or within certain time ranges. Use this, for example, to synchronize private events to your work calendar only if they affect your usual working times. See the reference for details.