[Iterable Lists] Adding logic to not create an audience if an existing audience already exists with the same name. #2511
+92
−32
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.
After testing Iterable Lists destination with the customer, we found out that the audience lifecycle tries to create an audience more than once, which it generates errors on Iterable, preventing the audience to sync correctly.
Here I add logic to first verify whether the corresponding list already exists. If it exists, the logic returns its id.
Testing