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