Calling getEntries right after a webook publish event doesn't always fetch the updated content

• Node Version: 8.11.1
• Npm Version: 5.6.0
• Platform: MacOS 10.13.4
• Package Version: 6.1.0

I’m using the webhook system to know when an entry has been published in my space. The webhook works fine and I’m getting the event on my server. But then, when I get the event, I’m calling getEntries to fetch the data related to my entry and all the links, and most of the time, the data I get is the old data, not the new one. I’ve found out that if I wait at least 20 seconds before calling getEntries, it will work fine and I’ll receive my updated data.

Any reason why calling getEntries when receiving the webhook result in out of date data?

The issue is particularly present when, on the webhook event, I need to fetch the parents entries (using links_to_entry, and finally calling getEntries on the final entries id. So the flow might be like this:

1. Receive webhook publish event
2. Calling getEntries with links_to_entry equals to the webhook entry id.
3. Potentially calling 2) multiple times
4. Once I have the entries I need, I’m calling getEntries again, but this time with include and sys.id set to what I need.
5. Notice that the result of 4) is not the updated content, but the old one. [Unless I wait 20 seconds before doing 4)]

[ilkka]

Won’t start a long discussion here, but @tleunen the method I described works for us with immediate updates, so no waiting for a sync. The downside is that we end up essentially maintaining a content cache (a microservice that does a full sync on boot and then incremental updates), but it lets us do our own tricks with how we resolve content for our UIs while still being able to use contentful’s tools for managing it.

[tleunen]

@ilkka Do you mean that the sync api doesn’t have the same limitations than the delivery api (waiting x seconds for the changes to be propagated)?