Data Quality Alert Emails

we automatically monitor the daily run of your data feed if we detect a problem that can impact calculations and reporting in the application, we send a “data checks alert action required” email to your technical/support contacts these alerts are triggered when one or more required files are in one of the following states outdated empty not found what’s inside the email the email contains a table like file – the filename we checked (e g , brands csv , suppliers csv , promotions csv ) last modified – the last modification timestamp we see for that file status / notes – detected status and an additional hint (for example “older than 360 hours” ) you may also see a note that your application data is not up to date because calculations are based on the latest available data on the data exchange server status definitions outdated meaning the file exists, but it hasn’t been updated within the expected time window (for example, “older than 24 hours”) impact the application may show stale results because we’re using older data example typical causes scheduled export didn’t run upload job failed (authentication, permissions, network, disk) file was generated but not delivered to the expected location timezone / scheduling drift (weekends/holidays not handled) how to fix ensure your export pipeline produced the newest file for the current period upload/replace the file in the data exchange location if required by your integration, notify our support team to trigger a manual re upload/reload empty meaning the file exists and is readable, but contains no records (or only headers) impact parts of the application may show missing entities (e g , no promotions/brands/suppliers) or incomplete calculations example typical causes upstream query returned zero rows due to filters/dates file truncation during generation or transfer incorrect delimiter/encoding causing records not to parse (appears “empty” to the importer) data source outage how to fix open the file and confirm it contains valid rows (not just headers) verify the export logic (filters, date ranges, joins) re upload the corrected file notify our support team if a reload is needed not found meaning we couldn’t find the file at the expected location/name at the time of the check impact the application cannot refresh the related dataset example typical causes filename changed (typo, different naming convention, different extension) file placed into a different folder/bucket upload process failed before delivery permissions changed (we can’t access it) how to fix confirm the file exists and matches the exact expected filename confirm it is in the correct path/location and accessible re upload if missing notify our support team if you need help validating the expected location/credentials recommended client action flow check the file content verify format, encoding, delimiter, headers, and that it contains the expected number of rows (see your integration manual for the file structure) re upload the updated file(s) upload to the agreed data exchange location using the same naming and structure notify us (if required) if your integration requires a manual trigger to reload/reprocess, contact support and mention affected file(s) status (outdated/empty/not found) time you re uploaded the fix