Unexpected Content and Date Issues¶
Column content doesn't match what the column name suggests, or date values fall outside expected ranges.
For an overview of all hygiene issue categories, see Data Hygiene Issues.
Unexpected column contains emails¶
This column is not labeled as email, but contains mostly email addresses.
| Likelihood | Possible |
| Quality dimension | Consistency |
| How it's detected | Flagged when profiling identifies an email pattern in a column whose name does not suggest email content. |
This could indicate shifted or switched source data columns.
Suggested action: Review your source data and follow up with data owners to determine whether the column should be populated with email addresses.
Unexpected column contains US states¶
This column is not labeled as a state, but contains mostly US state abbreviations.
| Likelihood | Possible |
| Quality dimension | Consistency |
| How it's detected | Flagged when profiling identifies US state abbreviations in a column with more than 5 distinct values whose name does not suggest state content. |
This could indicate shifted or switched source data columns.
Suggested action: Review your source data and follow up with data owners to determine whether the column should be populated with US states.
Unlikely dates out of typical range¶
Some date values in this column are earlier than 1900-01-01 or later than 30 years after the profiling date.
| Likelihood | Likely |
| Quality dimension | Accuracy |
| How it's detected | Flagged when any date value falls before 1900-01-01 or more than 30 years into the future. |
Dates outside this range are rarely legitimate in business data and may indicate data entry errors, placeholder values, or processing artifacts.
Suggested action: Review your source data and follow up with data owners to determine whether this data needs to be corrected or removed.
No table dates within one year¶
Among all date columns present in the table, none fall within one year of the profiling date.
| Likelihood | Possible |
| Quality dimension | Timeliness |
| How it's detected | Flagged when the most recent date across all date columns in the table is more than one year before the profiling date. |
This suggests the table may contain stale data that is no longer being updated.
Suggested action: Review your source data and follow up with data owners to determine whether dates in the table should be more recent.
No table dates within six months¶
Among all date columns present in the table, the most recent date falls six months to one year back from the profiling date.
| Likelihood | Possible |
| Quality dimension | Timeliness |
| How it's detected | Flagged when the most recent date across all date columns in the table falls between six months and one year before the profiling date. |
This is a softer signal than the one-year check — the data may still be current but is aging and worth monitoring.
Suggested action: Review your source data and follow up with data owners to determine whether dates in the table should be more recent.