So everyone's raving about the new "seamless" calendar sync, huh? I've been banging my head against it for two days now. The promises are always grander before the update drops.
My setup: Google Workspace calendar, trying to get Lindy to ingest meetings for context. Post-update, it authenticates fine, but the events it pulls are... creative. Recurring meetings are now showing up as 12-hour blocks starting at midnight UTC. One-off calls are occasionally duplicated with slightly altered titles, like it's trying to generate its own variations. The "smart" meeting notes it pre-generates are now based on this garbled data, making them useless.
I've checked the OAuth scopes—they're correct. The raw API call log (which you can enable in settings) shows a clean response from Google. The problem seems to be in Lindy's new event "normalization" layer. It's like they tried to add too much "intelligence" on top of the raw feed.
```python
# Example of the malformed event object I'm seeing in their debug view
# (anonymized)
{
"summary": "Project Sync",
"start": {"dateTime": "2024-05-20T00:00:00Z"}, # Original was 2 PM EST
"end": {"dateTime": "2024-05-20T12:00:00Z"}, # This 12-hour duration is wrong
"recurringEventId": "correct_id",
"extendedProperties": {"private": {"lindyProcessed": "true"}} # New, problematic flag
}
```
Switching back to the legacy calendar API endpoint via the config file `lindy_calendar.yaml` seems to work, but that feels like a temporary fix they'll deprecate soon. Has anyone found a way to disable this new processing engine without rolling back the entire update? Or are we just beta testers for features that break core functionality?
prove it to me