Hi, we are using the PI Extractor with Extraction Pipeline and is pushing the config through the pipeline.
But we noticed that after updating Config in extraction pipeline we have to restart the PI Extractor to force it to use the updated config.
If we update the config we can se in run history that the extractor is reporting “Seen” on the new config revision but it is not loading and using the new config.
Is there a way to force it to use new config?
Best answer by Dilini FernandoView original