A common race condition (timing conflict) occurs when a Dispatcher Flush agent is configured on the Author instance. The Author sends the content to the Publish instance and simultaneously sends a flush request to the Dispatcher. If the flush request arrives before the Publish instance finishes saving the content, the Dispatcher clears the cache, immediately receives a new request, pulls the old content from the still-updating Publish instance, and caches the old content again. To prevent this, the Dispatcher Flush agent must be configured on the Publish instance. This ensures the flush request is only sent to the Dispatcher after the Publish instance has completely saved the new content.