[Incident] CaaS Connect v3.85.0 – Unintended behavior change for remote datasets

Hi everyone,

We want to inform you about an issue introduced with CaaS Connect version 3.85.0, which was rolled out to FirstSpirit SaaS instances this Wednesday (February 18th, to DEV and QA last week, February 11th).

What happened?

With this version, references that point to remote datasets are directed to the remote project instead of to a local copy of the dataset, as was previously the case. This behavior should by default only apply to new projects. However we unintentionally changed how remote datasets are handled under a specific combination of conditions also for existing projects. This may lead to missing content in your front end.
We sincerely apologize for not catching this before the rollout.

Am I affected?

You are only affected if both of the following conditions apply to your project:

1. Your project uses remote datasets
2. The CaaS Connect project configuration has never been saved during the lifetime of the project — if any setting was ever changed, or the configuration dialog was closed with "Save" (even without making changes), you are not affected

You can double check point 2 by checking in the CaaS Connect project settings the setting of option "Handling of Remote Datasets", the original value before the update was "Use local copies of remote datasets".

If you are affected an effect is only visible if after Wednesday either

• new datasets were created in the remote source, or
• you executed one of the provided sync jobs in the affected project.

What are we doing about it?

We are currently compiling a list of affected customers and will reach out to them directly.

How can I revert to the previous behavior?

If you are affected, and we have not already reached out to you, you can restore the old behavior yourself:

1. Open the CaaS Connect project configuration
2. Change the toggle "Handling of Remote Datasets" to "Use local copies for remote datasets"
3. Save the configuration

This was the previous default value and will restore the expected behavior.

Questions?

If you have any questions or believe you are affected, please reach out to our Customer Support Team or your Customer Success Account Manager — they are happy to help.

We apologize for the inconvenience and the disruption this may have caused. We are  currently reviewing our release process to prevent similar issues in the future.

Thank you for your understanding.