Previously, they had the proper start and end time, but did not work correctly in Google Calendar and Microsoft Outlook regarding notifications or when travelling to another time zone.
When an error occurs during a scheduled run, ChronoLink now automatically plans another run for the next day. This retry attempt is useful because in most cases, connection errors are temporary.
Previously, a connection did not run again until you either triggered it manually or edited and saved it. You can still do that to force an immediate retry.
As before, if the last run failed, the connection is displayed with a ⚠️ status icon. The retry run will still happen, and if it is successful, the connection status is displayed as ✔️ again and the regular schedule resumes.
We have collected several kinds of temporary connection errors so far. Over time, we will add detection code for them, allowing ChronoLink to retry affected connections with a significantly shorter delay.
The connection queue system was rewritten from scratch. While nothing of this is visible to users, it is an important prerequisite for the next round of performance improvements. More on that in a future update.