Batches that stuck in forever loading state while doing batch ingestion from Azure Blob storage

Hi Team,

We are observing several hundred batch IDs that have been stuck in a “loading” state in 2 months period, which suggests potential data loss.

The source system successfully sent the data, however these batches never transitioned out of the loading state and appear to be stuck indefinitely. As a result, the data is not available downstream and we are currently missing critical data.

We have subscribed to dataflow ingestion alerts, but these alerts are not providing any visibility into batches that remain in the loading state, and no updates are triggered for these batch IDs.

Given that the data is now outdated and cannot be backfilled or re‑ingested, what is the most efficient and recommended approach to immediately identify, monitor, and detect batches that are stuck in the loading state?

we are using Retrieve list of batches with query params so that we can see the missing batches that are still in loading state 

Any suggestions would be appreciated 


Thanks
Reshmika