Data replication latency in the API?
Hello,
I started to notice a weird behavior starting a couple hours ago.
I use the API to create a new profile. Then when I make another API call to retrieve the same profile using its ID or email (or perform an operation on the profile), I will get an inconsistent behavior : sometimes I get the same response as if the profile did not exist (even one hour after its creation). I’m using API version 2024-10-15.
Example 1 :
https://a.klaviyo.com/api/profiles/?filter=equals(id%2C%2201KD6NQG7R8NZG14HD72635BSM%22) => will sometimes answer with the profile, sometimes with no profile.
Example 2 :
https://a.klaviyo.com/api/events/?filter=equals(profile_id%2C%2201KD6NQG7R8NZG14HD72635BSM%22) => will sometimes answer with the events linked to profile_id 01KD6NQG7R8NZG14HD72635BSM, and sometimes with a 400 HTTP status code with error message Profile ID 01KD6NQG7R8NZG14HD72635BSM does not exist. (I actually got a GUID for this request : a8012322-0d4e-486d-96ee-a7f24df1072a ).
Do you have any idea what this could be linked to and if there is a way to avoid it? Perhaps someone has already seen something like this?
It looks a bit like a data replication issue (in which the data is perhaps written to one database but not present in some other databases that may be used for other API calls). The status page does not seem to indicate any ongoing issue.
Thank you for reading!