Add faq that date string need to be ISO-8601 for time conditions to work #5698
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
There have been several tickets where customer's audiences did not work due to time conditions on traits where the date string is not in ISO-8601 format.
Added the following FAQ:
"Why is the time condition, such as a rolling time window condition of within last N number of days, configured on a trait not working in my audience?
For time conditions to work on a trait, please check that the date string of the trait is in ISO-8601 format. Further information on the date string requirement is mentioned in document on Spec: Common Fields regarding timestamp."
Merge timing
Related issues (optional)
Example tickets: