Per my knowledge, it is possible that your workflow step could advance to next step and cache is not yet published. It depends on your setup and network latency and size of content package to be replicated.
You could add a custom workflow step to listen/process the response code of replication action and then move to next step.