Hi Everyone,
First of all, I would like to wholeheartedly apologise for the inconvenience caused. We tried to pinpoint the issue today, but it turned out to be quite time-consuming.
What’s more, Google Apps Script — the platform used to run the connector — introduced restrictions to version management, meaning that only one of our developers could introduce fixes. Unfortunately, I could not find any details about this change in the official changelog.
What was the core issue? The most probable scenario is that, when we decided to deploy a new version of our Looker Studio connector, a platform update was running in the background. By “platform”, I mean Looker Studio. The connector update went through without any errors being thrown. However, we have since discovered that while some of the connector files were updated, others remained on the same version.
We’ll definitely look into additional methods of identifying such cases, but this is the first time this has happened to us and it wasn’t picked up by either Looker Studio or our connector. We have also looked through the Looker Studio community forum while debugging the issue. It looks like something was indeed happening to the platform, as different related issues popped up (example 1, example 2).