You may see “Missing Expected Files” alerts in your Full Workflow – All Daily Sources workflow, even though the source files are actually present in your Azure Blob storage.
This article explains why this happens and how you can fix it.
What’s Going On?
Some users noticed that several couriers were showing alerts for missing files (for example: Filename_yyyy_mm_dd_*.csv.gz), even though the files were confirmed to exist in the Azure Blob location.
Why This Happens
This issue occurs when an Azure snapshot process gets stuck in a “running” state but shows 0 duration.
Because the snapshot doesn’t complete properly, the new or updated files don’t become visible to downstream systems — leading Amperity to flag them as missing.
Once the stuck snapshot was cancelled and a new snapshot was triggered, all expected files appeared in the correct location and the alerts cleared.
How to Fix It
If you experience similar alerts, follow these steps:
- Check your Azure Blob location to confirm if the reported files are actually present.
- If they are missing or appear outdated, review the snapshot process for your data container.
- Cancel any snapshots that appear to be “in progress” with 0 duration.
- Trigger a new snapshot to refresh the data files.
- Once the snapshot completes successfully, rerun the affected Amperity workflows.
After these steps, the Missing Expected Files alerts should clear automatically, and the files will be processed as expected.