Prompt
why are my consent records missing timestamps
Latest observation
Nov 12, 2026
OpenAI APIWeb search: off
Consent records can be missing timestamps for a few common reasons:
-
The source system didn’t collect one
- Some consent flows only store a status like
opt_in/opt_outwithout a time field. - Legacy systems often record consent but not when it happened.
- Some consent flows only store a status like
-
The timestamp field exists but wasn’t populated
- A bug, integration issue, or partial import may have left it blank.
- Data migrations sometimes omit
created_at,updated_at, or event-time fields.
-
The timestamp is stored elsewhere
- It may be in an audit log, event table, or request metadata rather than the consent record itself.
- Sometimes it’s stored in a different timezone or nested JSON field.
-
Privacy or compliance handling removed it
- In some systems, timestamps are redacted or anonymized during export.
- De-identification pipelines can strip metadata unintentionally.
-
There was a parsing/ETL issue
- The field may have been present in the raw data but failed to map during ingestion.
- Format mismatches can cause the timestamp to be dropped.
-
The record was created manually
- Admin-entered or backfilled consent records may not have a precise event time.
If you want, I can help you troubleshoot this more specifically. For example:
- what system or database you’re using,
- what the consent record schema looks like,
- and a sample record with sensitive info removed.