Did you already try to remove the ElasticSearch index and generate it again? Deleting is also automatically done if you remove the export profile.
Otherwise I expecting an inconsistent config & data part of the export formate template.
You should also make sure not to execute the export with the same profile twice but set it up initially as scheduled and not touch it manually again.
Or if manually executed only re-trigger the export through process overview again and not directly on export profile as this may fire another instance causing a mix up in index generation. Just a thought...
Hi Stefan, There isn't a warning not to execute the export with the same profile twice documented anywhere! At least not that I've seen. It would make a good KB article. And if I didn't simply miss it in the installation and configuration manuals, it's probably a good idea to add it there too.
What I've been doing is setting up the export profile, executing it manually once using the PIM channel, then after successful completion I would execute from the profile again, but changing to a delta channel and running on a schedule. I'll try again, but this time I will re-trigger through process overview.
I've tried again. Manually executed one time with the PIM channel, then re-triggered from process overview, but I still get the same Error executing the export step Search index synchronization on the subsequent execution.
sorry my comment was more towards a possible follow up issue. The error should not ocurr in the first place.
My point was more around delta updates and how to setup the continuous stream of updating the search index on Elastic. We also have enhanced documentation with all forthcoming releases to be more explicit about that aspect:
On your actual issue, did you try to create a completely new index from scratch and see if the same appears? (i.e. general issue or index setup specific one?!)
Hey Stefan, if this error shouldn't be occurring should I submit a bug ticket? or is this already a known issue that R&D is working to fix?
In the meantime, I've just given up trying to use a delta channel.
I am not aware of an issue like this but to come up with a useful answer a couple of questions above the chain here should still get answers I get:
- Did you already try to remove the ElasticSearch index and generate it again? Deleting is also automatically done if you remove the export profile.
- did you try to create a completely new index from scratch and see if the same appears? (i.e. general issue or index setup specific one?!)
Any updates on that part? Or have you been able to narrow down specifics on how to reproduce this?
Yes I had tried removing the index and generating again, but I get the same results.
I also tried a completely new index in a different environment and get the same results again.
It's always the same... it runs fine on the initial execution, but subsequent executions (whether from the same profile, or repeating from the Process Overview) fail synchronization.
Well, I still thing it must be a config issue but running it with our support will certainly not harm.
Do you have a demo sandbox or anything or did you try the default templates we ship with the product as well to see if the vanilla setup we may provide you with already breaks in your setup?