Start batch jobs for stored keys on webhook trigger

Your stored dataset keys arrive without an automated runner, leaving batches idle and delaying model refreshes. Start jobs per key so data teams get processed inputs same day.

Start batch jobs for stored keys on webhook trigger

Overview

If dataset keys sit idle you can’t run timely model retrains and analysts waste time prepping batches; this flow retrieves stored keys on an external trigger and starts per-key jobs. It keeps pipelines moving and delivers training-ready inputs same day.

Start batch jobs for stored keys on webhook trigger