Hosted Extractor run trigger

We’re looking at this for hosted extractors in the context of the upcoming integrations feature, and in the context of workflows. ATM, the thinking is to add a way for the workflows capability to be informed by the hosted extractors that it’s “time to go”. 

One of the challenges are the “continuous flow of data” extractors - MQTT or Kafka for instance - where there’s no clear “I’m done” state.

The hosted extractors are designed to “run contenously”. I hear the desire to have a way to trigger them, but for 2025, this is beyond the scope of work the team can commit to. I will be parking this idea until further notice.

Could there be a better way to trigger the Hosted Extractor if it fails? Right now I have to change the interval of the job and pause/unpause it for it to trigger again. This is tedious when I’m troubleshooting.

​@Ben Petree - As mentioned, we’re looking at how Hosted Extractors and the upcoming Integrations feature will collaborate (a TBD feature combination at the moment). I would expect the extractors team to come back to this in a quarter or two.