Stale data returned in Secrets automation flow

Hi all!

My apologies for the late response here. We are doing a deep investigation into what is going on here. So far, we have not been able to reproduce the issue, but with some extra info we may be able to.

So could one or more of you help me with the following points:
1. In your case, is Connect running continuously or is it started just before it is needed?
2. Do you have any logs of the containers (both connect-api and connect-sync) for a time that you ran into this issue? If possible, from the moment Connect started until you made a request that returned stale data.
3. Have you always had this problem? Or did it only start showing up after a while? In case of the latter, do you have an indication of how long it took for the problem to manifest itself?
4. How are you running Connect? (docker-compose, AWS ECS, k8s/Helm, etc)
5. Which version of Connect are you running?
6. Which Connect integrations (SDK, Terraform provider, Ansible plugin, etc, or just plain cURL) do you use?

Answers to these questions could possibly help us reproduce the issue

In the meantime, we are also working on some more general improvements to the syncing mechanism, that should make it more robust.

Joris