User Token is not taken for validation as Email is not in valid format. #4723
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
Email and User Token both fields are mapped in "Send custom behavioural event" mapping and sent over the event paylaod too. But the event is failing for delivery with "Payload validation error" as the email is not in valid format, why it is not taking the User token for validation? Event payload should have the email with valid format or empty string, so that the user token will take precedence and can be validated. An invalid email will not pass mapping validation. Hence the event delivery is failing.
Merge timing
Related issues (optional)