Error Library / AEP
XDM error: invalid date-time format in timestamp fields
What you see
Field 'timestamp' expected type 'date-time' but got '01-05-2024 10:15'XDM date-time fields expect ISO 8601 / RFC 3339 values such as 2024-05-01T10:15:00Z. Regional formats like 01-05-2024 10:15 are ambiguous (1 May or 5 January?) and are rejected.
Why it happens
- Spreadsheets and regional exports write dates as DD-MM-YYYY or MM/DD/YYYY, often without a time zone.
- A date-only value sent to a date-time field, or a date-time sent to a date field, also fails.
- Missing time zones are a silent risk even when a value is accepted: 10:15 in India and 10:15 in London are different moments.
How to fix it
- Convert dates to ISO 8601 before or during ingestion: 2024-05-01T10:15:00+05:30 or 2024-05-01T04:45:00Z.
- Decide the source time zone explicitly instead of letting it default.
- Use a mapping transformation during ingestion when you can't change the export.
- Spot-check a few converted rows against the source, especially dates where the day is 12 or lower, since those are the ones that can be read either way.
Before and after
Fails
{ "timestamp": "01-05-2024 10:15" }Works
{ "timestamp": "2024-05-01T10:15:00+05:30" }Common questions
Is 2024-05-01 10:15:00 (with a space) accepted?
Treat it as invalid. Use the T separator and include a time zone or Z for UTC.
Practise the fix
Build the Customer Profile
Reproduce this error in your own AEP practice workspace, fix it, and earn a verifiable credential for the skills involved: XDM schema design, Identity descriptors, Real-Time Customer Profile enablement, Dataset configuration.
Related errors
XDM ingestion error: "Missing required field" (_id, timestamp)
XDM error: number field received text (currency symbols, commas)
AdsBot is an independent training provider, not affiliated with Adobe. Behaviour can differ between ingestion methods and product versions; always test with a small batch first.